Totally-safe-transmute Alternatives

totally-safe-transmute reviews and mentions

• Zlib-rs is faster than C
  10 projects | news.ycombinator.com | 16 Mar 2025
• Sudo Replacement
  4 projects | news.ycombinator.com | 20 Jan 2023

  For example, there is this (pure safe Rust) code: https://github.com/ben0x539/totally-safe-transmute/blob/main... which accesses external resources (/proc/self/mem) in order to violate the safety guarantees.

• A rust crate that lets you compress ASCII text to a single Unicode "character"
  5 projects | /r/rust | 17 Nov 2022

  The first is the totally_safe_transmute crate. I mean, who wouldn't love library code that has .expect("welp") and .expect("oof") as its error handling? But that's not even the really scary part. Issue #2 ("i hate this") remains open to this day, but for obvious reasons there's no chance of resolution. This post has some context and a line-by-line explanation of how it works.

• What do you expect from Rust in 2023?
  9 projects | /r/rust | 4 Aug 2022

  You mean like this?

• In C# you can transmute without `unsafe`
  3 projects | /r/rustjerk | 23 Feb 2022

  You can also do that in rust on linux: https://github.com/ben0x539/totally-safe-transmute/blob/master/src/lib.rs

• Why choose Rust
  2 projects | /r/rust | 24 Jan 2022

  I want to correct this statement: Rust can be safer, but not if a library you use contains unsound code. Unsoundness is most often caused by unsafe code, but not always (totally_safe_transmute, anyone?). There is a misconception that unsafe code blocks are always unsound and should be avoided at all costs, but they're completely fine if the safety contracts are upheld. In fact, unsafe blocks isolate the potential issues to make it easier to identify where undefined behavior may be occurring. unsafe code blocks are a feature of the language, and their usage should not be viewed as opting out of any safety the language provides, imo.

• "# NONONONONONO DON'T YOU FUCKIN' DARE the safety features are there so that your programs aren't filled to the brim with security vulnerabilities. Unless you care A LOT(And I mean A LOT A LOT) about compile times, never use `unsafe`."
  1 project | /r/programmingcirclejerk | 19 Jan 2022

  Just reimplement totally_safe_transmute in Zig. No need for unsafe.

• I mean, it solves most library conflicts
  1 project | /r/rustjerk | 14 Jan 2022

  Why transmute() when you can totally_safe_transmute()?

• Safe Transmute
  1 project | news.ycombinator.com | 12 Dec 2021
• Static Analyzer Rudra Found over 200 Memory Safety Issues in Rust Crates
  6 projects | /r/rust | 14 Nov 2021

  Well, there is always the totally-safe-transmute.

• A note from our sponsor - SaaSHub
  www.saashub.com | 30 Apr 2025

  SaaSHub helps you find the best software and product alternatives Learn more →