Unsound implementation in `memory::{any_as_bytes, any_slice_as_bytes}` about rafx HOT 3 CLOSED

I can see the result of this being undefined in the sense that the padding bytes could be any value. I don't expect in practice this would cause real problems such as an actual crash.

This function is very much meant for low-level work with data (like memcpy of structs to GPU memory) and potentially having junk in the padding bytes would be acceptable and expected behavior.

from rafx.

It's true that it is hard to cause to crash here. But from perspective of safety, undefined behavior is not allowed to happen in safe function anyway. From the concept of the programming language, this function should be declared as unsafe.

from rafx.

As noted in the readme, this project does not follow typical guidance for the usage of unsafe. (https://github.com/aclysma/rafx#safety)

from rafx.