rust
totally-safe-transmute | rust | |
---|---|---|
17 | 9 | |
245 | 4,997 | |
- | 0.9% | |
0.0 | 5.2 | |
over 1 year ago | 5 months ago | |
Rust | Rust | |
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
totally-safe-transmute
-
Sudo Replacement
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"
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?
You mean like this?
-
In C# you can transmute without `unsafe`
You can also do that in rust on linux: https://github.com/ben0x539/totally-safe-transmute/blob/master/src/lib.rs
-
Why choose Rust
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`."
Just reimplement totally_safe_transmute in Zig. No need for unsafe.
-
I mean, it solves most library conflicts
Why transmute() when you can totally_safe_transmute()?
- Safe Transmute
-
Static Analyzer Rudra Found over 200 Memory Safety Issues in Rust Crates
Well, there is always the totally-safe-transmute.
-
// SAFETY: NO
They should use https://github.com/ben0x539/totally-safe-transmute
rust
-
Have you ever wanted a library to check for 69 in a string?
You can use Tensorflow for Rust to simplify that task and avoid pain with regex. Just have the right mindset.
- Rust vs cpp for a new engineer to autonomous vehicles and robotics
-
Making a better Tensorflow thanks to strong typing
What is the benefit of this compared to using bindings/a wrapper to Tensorflow, or other ML libraries written in C/C++, such as this community hosted project on tensorflow's github. If it's just for fun that is a valid enough reason imo, just curious since you describe it as a better Tensorflow because of the typing vs using the python wrapper, when there already exist ways to interact with tensorflow with both Rust and other statically typed languages, also including C++ (officially supported), C#, Haskell and Scala, as well as probably having bindings not mentioned on the documentation for more niche languages.
-
Integrating machine learning models into Rust applications?
(3) You could use TensorFlow as your executor: https://github.com/tensorflow/rust
-
Why Static Languages Suffer From Complexity
TensorFlow has language support for TypeScript well as Rust.
-
Is PyO3 library production ready?
Thank you for the restponse! With tensorflow I am probably better of with something like; [tensorflow rust bindings](https://github.com/tensorflow/rust/tree/master/src). But I believe some useful extensions are still written in python for example; [TFDV](https://github.com/tensorflow/data-validation).. and how about scikit-learn or even something that is simpler like fb-prophet that is entirely written in python?
-
How mature is the QT integration?
Tensorflow bindings exist, technically, but they're in a pretty rough state AFAIK.
- Feasibility of Using a Python Image Super Resolution Library in My Rust App
-
Rusticles #10 - Wed Sep 09 2020
tensorflow/rust (Rust): Rust language bindings for TensorFlow
What are some alternatives?
tinyvec - Just, really the littlest Vec you could need. So smol.
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
tamago - TamaGo - ARM/RISC-V bare metal Go
leaf - Open Machine Intelligence Framework for Hackers. (GPU/CPU)
usbarmory - USB armory - The open source compact secure computer
anyhow - Flexible concrete Error type built on std::error::Error
advisory-db - Security advisory database for Rust crates published through crates.io
Rustup - The Rust toolchain installer
UnsoundCrates - Black list of all crates that promotes unsoundness
rusty-machine - Machine Learning library for Rust
project-safe-transmute - Project group working on the "safe transmute" feature
solana - Web-Scale Blockchain for fast, secure, scalable, decentralized apps and marketplaces.