We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
2 parents ea58235 + 3809d60 commit c85eef1Copy full SHA for c85eef1
text/1857-stabilize-drop-order.md
@@ -128,7 +128,7 @@ in the future.
128
129
Closure captures are also dropped in unspecified order. At this moment, it seems
130
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/)
+the closure (see [this blog post](https://ochagavia.nl/blog/exploring-rusts-unspecified-drop-order/)
132
for more details). Again, this order is closely tied to an implementation that
133
we may want to change in the future, and the benefits of stabilizing it seem small.
134
Furthermore, enforcing invariants through closure captures seems like a terrible footgun
0 commit comments