From 3809d607cc06215dc736ad8be0f6e92d2f3003bd Mon Sep 17 00:00:00 2001 From: Jeroendevr Date: Tue, 13 Dec 2022 14:28:53 +0100 Subject: [PATCH] Update link to blog post Website is not accessible on the GitHub.io domain. So change to the current domain. --- text/1857-stabilize-drop-order.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/text/1857-stabilize-drop-order.md b/text/1857-stabilize-drop-order.md index fca153e6918..980769553ae 100644 --- a/text/1857-stabilize-drop-order.md +++ b/text/1857-stabilize-drop-order.md @@ -128,7 +128,7 @@ in the future. Closure captures are also dropped in unspecified order. At this moment, it seems like the drop order is similar to the order in which the captures are consumed within -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/) for more details). Again, this order is closely tied to an implementation that we may want to change in the future, and the benefits of stabilizing it seem small. Furthermore, enforcing invariants through closure captures seems like a terrible footgun