maturin
totally-safe-transmute | maturin | |
---|---|---|
17 | 37 | |
245 | 3,275 | |
- | 3.1% | |
0.0 | 9.4 | |
over 1 year ago | 5 days 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
maturin
-
In Rust for Python: A Match from Heaven
This story unfolds as a captivating journey where the agile Flounder, representing the Python programming language, navigates the vast seas of coding under the wise guidance of Sebastian, symbolizing Rust. Central to their adventure are three powerful tridents: cargo, PyO3, and maturin.
-
Feedback from calling Rust from Python
-- Maturin on GitHub
-
Some Reasons to Avoid Cython
My new favorite way to write very fast libraries for Python is to just use Rust and Maturin:
https://github.com/PyO3/maturin
It basically automates everything for you. If you use it with Github actions, it will compile wheels for you on each release for every platform and python version you want, and even upload them to PyPi (pip) for you. Everything feels very modern and well thought out. People really care about good tooling in the Rust world.
-
Which programming language to focus on for my PhD journey in bioinformatics?
Python first, you will be able to experiment quickly with the notebooks. Then maybe write (or rewrite) some modules in Rust that you can expose as python modules, with py03 and maturin. Feel free to publish useful packages on both crates.io and pypi.org, so you can contribute to Python and Rust ecosystems.
-
python to rust migration
Now if you really want to use Rust, you can rewrite only the part that are slowing down your consumer. It's easy by using Py03 and maturin. Maybe also rayon to parallelize.
-
Ask HN: Is it worth it for me to learn Go or Rust as a Data Engineer?
It's relatively easy to extend Python with project like Py03[0] and Maturin[1]. Polars[2] is the perfect example of that.
It's not easy to push coworkers/companies to use an unfamiliar language. Rust isn't fast to learn. You need very good arguments and a good usecase to make it works.
I doubt that learning Rust will help you more that learning more about the data engineers tools, so this isn't really "worth" your time.
[0] -- https://pyo3.rs/v0.18.3/
[1] -- https://github.com/PyO3/maturin
[2] -- https://www.pola.rs/
- Rust CLI app installable via PIP?
-
Blog Post: Making Python 100x faster with less than 100 lines of Rust
In this case, PyO3/maturin does all the setup and getting the module into Python. They also have docs going into a lot more depth on this.
-
Is Rust faster than Python out of the box
Lastly if you're willing to introduce Rust, I'd consider a gradual approach using native libraries built in rust with PYO3. Check the maturin guide that helps you to streamline the build process of native libraries : https://github.com/PyO3/maturin . From there you could try to find hotspots in your python app and replace those with a native implementation.
- sccache now supports GHA as backend
What are some alternatives?
tinyvec - Just, really the littlest Vec you could need. So smol.
Poetry - Python packaging and dependency management made easy
tamago - TamaGo - ARM/RISC-V bare metal Go
setuptools-rust - Setuptools plugin for Rust support
rust - Rust language bindings for TensorFlow
termux-packaging - Termux packaging tools.
usbarmory - USB armory - The open source compact secure computer
PyOxidizer - A modern Python application packaging and distribution tool
advisory-db - Security advisory database for Rust crates published through crates.io
rust-numpy - PyO3-based Rust bindings of the NumPy C-API
UnsoundCrates - Black list of all crates that promotes unsoundness
pybind11 - Seamless operability between C++11 and Python