Anybody know of any good resources on when it's ok to mark @rustlang functions that use unsafe code as safe? I feel like while there's been some good highly technical analysis, there's not a ton of resources of how to think about `unsafe`.
Other libraries have taken a different approach. It can be argued that ash is more successful than vulkano precisely because it doesn't try to hide the inherent unsafety of Vulkan.
-
-
A blog post is probably a better place for this than a Twitter rant. I have a doc with an outline for it (shared with Ryan already) but limited time to blog these days :/
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.