gitmoji
totally-safe-transmute | gitmoji | |
---|---|---|
17 | 62 | |
245 | 15,295 | |
- | - | |
0.0 | 8.9 | |
over 1 year ago | 8 days ago | |
Rust | TypeScript | |
- | MIT License |
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
gitmoji
-
Git commit helper: add emojis to your commits
This project provides an easy solution for using gitmoji from your command line. Gitmoji-cli solves the hassle of searching through the gitmoji list. Includes a bunch of options you can play with! 🎉
-
What is a good message and size for a commit?
Gitmoji ✨ add integration with xpto
- Gitmoji
- Introducing my Lightweight PHP Framework: Simplifying Small Projects with a Powerful Core!
-
jsDevStarterPack
Do not forget to use emojis in your commit messages. https://gitmoji.dev/
- Git sloppiness and obsessively compulsively committing to the remote repo
-
OpenCommit: GitHub Action to improve commits with meaningful messages on every `git push` 🤯🔫
You may also turn on GitMoji convention if you prefer your messages baked with emojis 🤠
-
Show HN: Gut – An easy-to-use CLI for Git
I use Gitmoji:
https://github.com/carloscuesta/gitmoji
-
Which "Conventional Commit" Type To Use When Just Adding Comments To Source File?
If you are a fan of gitmoji (I am not - but its something some people seem to like) https://gitmoji.dev
-
OpenCommit: GPT CLI to auto-generate impressive commits in 1 second 🤯🔫
The lib uses conventional commits convention which makes commits meaningful. You can also turn on GitMoji setting if you like. And select different languages and many other features (I got 12 PRs so far)
What are some alternatives?
tinyvec - Just, really the littlest Vec you could need. So smol.
semantic-release-gitmoji - ✨🐛💥 A semantic-release plugin for gitmojis. Different from conventional changelog, Gitmoji commits are used to determine a release type and generate release notes.
tamago - TamaGo - ARM/RISC-V bare metal Go
cz-customizable - A standalone commit message helper or customizable commitizen adapter for https://github.com/commitizen/cz-cli
rust - Rust language bindings for TensorFlow
semantic-release - :package::rocket: Fully automated version management and package publishing
usbarmory - USB armory - The open source compact secure computer
marktext - 📝A simple and elegant markdown editor, available for Linux, macOS and Windows.
advisory-db - Security advisory database for Rust crates published through crates.io
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
UnsoundCrates - Black list of all crates that promotes unsoundness
Vim - The official Vim repository