It's kinda funny, we could probably just literally copy-paste what chromium is doing and we'd see some massive wins. I actually think another Boost library _would_ be useful because it'd enable us to start ushering in other chromium patterns, like their span utilities from the Unsafe Buffers guidelines: https://chromium.googlesource.com/chromium/src/+/main/docs/unsafe_buffers.md Functions like `byte_span_from_ref` are absolutely fantastic and amazing to use, and honestly they belong in Boost too. Boost.Core is probably the wrong place because we should want to add a whole bunch of stuff like this and it'd be good to have it all in one nice and easy place. Now, all that being said... we should probably compare the implementations from the std proposals, what chromium is doing and we should also take into account what Rust's CStr is doing as well. These impls have their own divergences we should compare and contrast. - Christian