From 66328488332ac612b119a827a68895a1cf614455 Mon Sep 17 00:00:00 2001 From: Nilstrieb <48135649+Nilstrieb@users.noreply.github.com> Date: Sat, 23 Jul 2022 21:17:54 +0200 Subject: [PATCH] add note about rustc --- content/posts/box-is-a-unique-type.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/posts/box-is-a-unique-type.md b/content/posts/box-is-a-unique-type.md index 64ad2d9..746ea4f 100644 --- a/content/posts/box-is-a-unique-type.md +++ b/content/posts/box-is-a-unique-type.md @@ -212,7 +212,7 @@ There is one clear potential benefit from this box behaviour: ✨Optimizations that can bring clear performance wins (for `noalias` on `&mut T`, those were measureable). So the only question remains: **How much performance does `noalias` on `Box` give us now, and how many potential performance improvements could we get in the future?** For the latter, there is no simple answer. For the former, there is. `rustc` has [_no_ performance improvements](https://github.com/rust-lang/rust/pull/99527) -from being compiled with `noalias` on `Box`. +from being compiled with `noalias` on `Box`, but this isn't really representative since rustc mostly uses arenas instead of box internally. I have also benchmarked a few crates from the ecosystem with and without noalias on box, and the [results](https://gist.github.com/Nilstrieb/9a0751fb9fd1044a30ab55cef9a7d335) were inconclusive. (At the time of writing, only regex-syntax, tokio, and syn have been benchmarked.) regex-syntax showed no changes. Tokio showed a few improvements without noalias