Unsound usages of unsafe implementation from `AsciiStr` to `wider: ty` about rust-ascii HOT 2 CLOSED

The macro is only invoked with [AsciiChar], [u8] and str, and is not exported.
So I don't think there's any actual "unsound usages".

Is the problem that the macro doesn't check that the type has the same size and alignment as AsciiStr?
All the types it's used with are unsized, so std::mem::align_of::<$wider>() won't compile, and even if it worked it wouldn't reject [bool] which would also be unsound.
I can agree the macro has sharp edges though, and I'll accept a PR replacing widen_box! with direct implementations.

from rust-ascii.

Yes, thanks for your reply! Since it's a static analysis, it would be an approximate of all the possibilities. If it's carefully used, there won't be issues.

from rust-ascii.