konsumlamm

Now we have two possible implementations xD (see #162). I don't think using `&mut ManuallyDrop` makes a difference here, as dropping a `&mut` doesn't do anything anyway. I don't see...

I don't see the point of this new method. What advantage does it have over `reset`? What do you mean by "keep expected memory size"?

What exactly is the point of this? What's wrong with `value = getEnv(...)`?

> how about `mapItContainer` ? Since it maps directly on the AST, I think `mapItAst` would be a good name.

What exactly is the point of this? Now people can't read about `notnil` at all. I think this should only be removed from the experimental docs when it's actually stable...

So if I understand correctly, the `Flag` enum would only be used for stuff like iterating and inserting single flags? Because the result of operations like `|` couldn't be stored...

I like it! No complaints from me.

There are some issues that I'd like to see getting fixed, but I'm not sure if that would be a breaking change: * https://github.com/bitflags/bitflags/issues/137 * https://github.com/bitflags/bitflags/issues/236

> This should now be supported. Can you please verify? Doesn't seem to work for me.

You can already do that with `const_assert` (since `size_of` is a `const fn`), for example: ```rs use std::mem::size_of; const_assert!(size_of::()