Closed mutantbob closed 2 years ago
The doc comments look good, but I would appreciate keeping the unsafe
keywords, in fact, I was planing to enable:
#![feature(unsafe_block_in_unsafe_fn)]
#![deny(unsafe_op_in_unsafe_fn)]
However, there are a few unsafe fn
s that need even more unsafe
s for that, that's why I haven't enabled it yet. It's on my to-do list.
I added the
include_str!
example we were talking about. I also removed someunsafe
keywords that the compiler said were unnecessary. I know it has demanded the unsafe keyword in other instances of an unsafe function body, but I don't know all the subtleties.