Skip to content

Commit 3809d60

Browse files
author
Jeroendevr
authored
Update link to blog post
Website is not accessible on the GitHub.io domain. So change to the current domain.
1 parent ea58235 commit 3809d60

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

text/1857-stabilize-drop-order.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -128,7 +128,7 @@ in the future.
128128

129129
Closure captures are also dropped in unspecified order. At this moment, it seems
130130
like the drop order is similar to the order in which the captures are consumed within
131-
the closure (see [this blog post](https://aochagavia.github.io/blog/exploring-rusts-unspecified-drop-order/)
131+
the closure (see [this blog post](https://ochagavia.nl/blog/exploring-rusts-unspecified-drop-order/)
132132
for more details). Again, this order is closely tied to an implementation that
133133
we may want to change in the future, and the benefits of stabilizing it seem small.
134134
Furthermore, enforcing invariants through closure captures seems like a terrible footgun

0 commit comments

Comments
 (0)