ziglings
cargo-geiger
Our great sponsors
ziglings | cargo-geiger | |
---|---|---|
36 | 30 | |
4,030 | 1,296 | |
- | 1.5% | |
8.1 | 5.4 | |
about 1 month ago | 4 days ago | |
Zig | Rust | |
MIT License | GNU General Public License v3.0 or later |
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.
ziglings
-
Roadmap to master zig
Master syntax - language possibilities, so that you can read code. Ziglings (or github) does great job teaching it!
-
Problems of C, and how Zig addresses them
I am interested to learn, how Traits in Rust and Interfaces in Go behave differently from this concept.
[1] https://github.com/ratfactor/ziglings/blob/main/exercises/09...
-
What's the reasoning behind the iguana mascot, and why is Zig specifically named so?
Is Zero the space lizard (dinosaur?) with the hammer in the picture in Ziglings' readme? (I like this guy)
-
What “sucks” about Zig?
Also, https://github.com/ratfactor/ziglings if you missed it.
-
Ask reddit: What learning resources have taught you the most about zig?
Along with ziglearn, I also found ziglings useful.
- Bun v0.5
-
Thinking of learning Zig and systems programming
I suggest to learn by fixing tiny broken programs: https://github.com/ratfactor/ziglings
-
Ask HN: What is the coding exercise you use to explore a new language?
+1 for rustlings, which also inspired "ziglings" [1]. Both of these were great resources for quickly & easily learning the basics of their respective languages.
- How to get started with ziglang?
-
My views on Ziglang
Ziglings
cargo-geiger
-
Was Rust Worth It?
Instead of looking at the crates themselves, you might want to check your (or others') Rust application with https://github.com/rust-secure-code/cargo-geiger to get a sense of effective prevalence. I also dispute that the presence of unsafe somewhere in the dependency tree is an issue in itself, but that's a different discussion that many more had in other sub-threads.
-
Found a language in development called Vale which claims to be the safest AOT compiled language in the World (Claims to beSafer than Rust)
There's still plenty. Run cargo geiger on any of your projects and see for yourself.
- pliron: An extensible compiler IR framework, inspired by MLIR and written in safe Rust.
-
[Discussion] What crates would you like to see?
You can use cargo-geiger or cargo-crev to check for whether people you trusted (e.g. u/jonhoo ) trust this crate.
-
How do you choose what crate you will use?
The amount of unsafe code is also a factor. cargo geiger is a handy tool for measuring it.
-
Rosenpass – formally verified post-quantum WireGuard
For that, I believe you need to use cargo-geiger[0] and audit the results.
-
Hey Rustaceans! Got a question? Ask here (6/2023)!
cargo-geiger is a subcommand you can install which will check all the crates in your dependency graph for unsafe blocks and print out a report (which also shows if a crate has #![forbid(unsafe_code)] or not). You can then inspect those crates' sources to judge their use of unsafe for yourself. I don't think it has a "check" mode that simply errors if your dependency graph contains unsafe though, it's more about just collecting that information.
-
The most creative, funny, clever, ridiculous, ... library names!
Technically a binary, not a library, but cargo-geiger, which detects usages of unsafe code in dependencies.
-
Should we be worried about proliferation of unsafe in Rust code?
I know that cargo-geiger exists but apparently most people don't care, which is not a good sign. Should we be worried about this? Are there plans to fight and decrease the use of unsafe in Rust code? At least maybe make the core primitives like Rc or Vec safe?
-
Security advisory: malicious crate rustdecimal | Rust Blog
Or rather, the only thing it guarantees is that in certain parts of the code (the parts you don't trust) you can't use unsafe stuff. Which is exactly what #![forbid(unsafe_code)] does! Or some use of https://github.com/rust-secure-code/cargo-geiger or something.
What are some alternatives?
awesome-zig
Rustlings - :crab: Small exercises to get you used to reading and writing Rust code!
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
nrf-hal - A Rust HAL for the nRF family of devices
xtensa-zig - Zig built against xtensa fork of LLVM for targetting ESP32
rust-koans - Koans for the Rust programming language
bacon - background rust code check
STL - MSVC's implementation of the C++ Standard Library.
TinyGo - Go compiler for small places. Microcontrollers, WebAssembly (WASM/WASI), and command-line tools. Based on LLVM.
rust - Empowering everyone to build reliable and efficient software.
node - Node.js JavaScript runtime ✨🐢🚀✨
nomicon - The Dark Arts of Advanced and Unsafe Rust Programming