debug_unsafe 0.1.4

Uses `debug-assertions` as a switch of safe/unsafe behaviour

Coverage
0%
0 out of 11 items documented0 out of 7 items with examples
Size
Source code size: 17.58 kB This is the summed size of all the files inside the crates.io package for this release.
Documentation size: 1.32 MB This is the summed size of all files generated by rustdoc for all configured targets
Ø build duration
this release: 23s Average build duration of successful builds.
all releases: 14s Average build duration of successful builds in releases after 2024-10-23.
Links
RoDmitry/debug_unsafe
1 0 0
crates.io
Dependencies
- arraystring ^0.3 normal optional
Versions
Owners

Debug Unsafe (Rust)

Uses debug-assertions compiler flag as a switch of safe/unsafe behaviour. It's mainly used for tests to trigger panic instead of UB in unsafe calls.

If you want an extra safe (but less performant) behaviour, or need to catch an UB, you can enable debug-assertions (safe behaviour):

only for this library in Cargo.toml with:

[profile.release.package.debug_unsafe]
debug-assertions = true

globally in a command line with: RUSTFLAGS="-C debug-assertions" cargo build --release (requires cargo clean first, if it was previously built without the flag).