no-panic
rust-quiz
no-panic | rust-quiz | |
---|---|---|
12 | 11 | |
515 | 1,580 | |
- | - | |
4.2 | 6.2 | |
about 2 years ago | 24 days ago | |
Rust | Rust | |
GNU General Public License v3.0 or later | Creative Commons Attribution Share Alike 4.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.
no-panic
-
no_panic causing errors in hello world?
I discovered a crate called no_panic that prevents a function from compiling, unless the compiler can proof that this function can't panic.
-
Is there something like "super-safe" rust?
/u/dtolnay has a no-panic macro, I don't know its limitations but in older comments they note it pretty much has to be used in release mode, as there are lots of panic codepaths which get optimised out.
-
Is Rust really safe? How to identify functions that can potentially cause panic
'Hacks' such as https://github.com/dtolnay/no-panic, https://crates.io/crates/no-panics-whatsoever that ensure any calls to panic handling will result in link errors. Not really reliable in terms of being able to abort instead, but a possible tool.
-
US NGO Consumer Reports also reporting on C and C++ safety for product development.
nope. Unfortunately, no mainstream language has this yet. We need an Algebraic effects typesystem to do this properly. There are a few temporary band-aid solutions like https://github.com/dtolnay/no-panic
-
Carefully exploring Rust as a Python developer
This kind of already exists in the form of #[no_panic] [1]?
> If the function does panic (or the compiler fails to prove that the function cannot panic), the program fails to compile with a linker error that identifies the function name.
1: https://github.com/dtolnay/no-panic
- What I like about rust
-
LKML: Linus Torvalds: Re: [PATCH v9 12/27] rust: add `kernel` crate
I really think that Rust needs an official #[no_panic] macro that can validate these sort of things (like dtolnay’s crate, I’m not sure why it was archived)
-
A pair of Linux kernel modules using Rust
Because it's convenient and familiar to most programmers. Not providing bounds-checked indexing makes some kinds of code very hard to write.
But note his problem also happens with integer division.
In Rust, a[x] on an array or vec is really a roughly a shortand for a.get(x).unwrap() (with a different error message)
Likewise, a / b on integers is a kind of a shortand for a.checked_div(b).unwrap()
The thing is, if the index ever is out of bounds, or if the denominator is zero, the program has a bug, 100% of time. And if you catch a bug using an assertion there is seldom anything better than interrupting the execution (the only thing I can think of is restarting the program or the subsystem). If you continue execution past a programming error, you may sometimes corrupt data structures or introduce bizarre, hard to debug situations.
Doing a pattern match on a.get(x) doesn't help because if it's ever None (and your program logic expects that x is in bounds) then you are kind of forced to bail.
The downside here is that we aren't catching this bug at compile time. And it's true that sometimes we can rewrite the program to not have an indexing operation, usually using iterators (eliding the bounds check will make the program run faster, too). But in general this is not possible, at least not without bringing formal methods. But that's what tests are for, to ensure the correctness of stuff type errors can't catch.
Now, there are some crates like https://github.com/dtolnay/no-panic or https://github.com/facebookexperimental/MIRAI that will check that your code is panic free. The first one is based on the fact that llvm optimizations can often remove dead code and thus remove the panic from a[x] or a / b - if it doesn't, then compilation fails. The second one employs formal methods to mathematically prove that there is no panic. I guess those techniques will eventually be ported to the kernel even if panics happen differently there (by hooking on the BUG mechanism or whatever)
-
Redoing the runtime
Hmm, yeah as you mentioned, looks like a surprising amount of stuff is already done in the rust for the linux kernel project: https://github.com/Rust-for-Linux/linux/tree/rust/rust/. It's also MIT/Apache licensed, but I was expecting gpl, so I can actually use it. It's still a lot to trim down on, so might be easier to just build up as needed. Additionally I just saw /u/dtolnay's #[no_panic] attribute which at least makes it a compiler error if it's accidentally done.
-
[PATCH 00/13] [RFC] Rust support
Obviously, in bare metal systems, in the kernel, etc, you always want to use the second style. In this patch series, the first type had been stubbed out to panic, but Linus doesn't want any chance of panicking, he wants it to be a compile time error if anyone tries to call these methods from within the kernel, for example by not providing the symbols and failing to link if someone did try to use them. There is already precedent for doing that in the Rust ecosystem, so it's planned to do that in this patch series, but the authors hadn't gotten to that yet.
rust-quiz
-
So you think you know C?
If you didn't like these because they're "trick" questions you likely also would not enjoy CppQuiz (https://cppquiz.org/)
However you might well enjoy https://dtolnay.github.io/rust-quiz/
Like the C++ quiz, "Undefined Behaviour" is a valid answer, however, the quiz questions are about safe Rust, so that answer is always wrong.
I still get more than half of them wrong unless given far too long to think about it.
-
Introducing the "Rust Interview Handbook" - Your Go-To Resource for Rust Interview Success! 💪
Cool, but I feel like the current questions are super basic. Something you're able to answer after reading the book and toying with Rust on a weekend. Definitely needs some harder questions, maybe feel inspired by https://dtolnay.github.io/rust-quiz/?
-
The Usability of Advanced Type Systems: Rust as a Case Study
> If we accept that Rust is indeed more difficult to learn than comparable systems programming languages
My problem is with "comparable systems programming languages". To me the only thing that fits there today is C++ and while a great many programming languages would be easier to learn than Rust, C++ is not one of them by a long shot.
I think the C++ Quiz https://cppquiz.org/ and the Rust Quiz https://dtolnay.github.io/rust-quiz/ illustrate handily. Neither of these languages is a walk in the park, but, notice they both have "Undefined behaviour" as a possible answer? Safe Rust doesn't actually have undefined behaviour, so you get to rule out one of the possibilities any time you don't see the "unsafe" keyword, which is in fact every time on the Rust Quiz. In C++ some of the quiz questions invoke UB, but good luck correctly guessing which ones.
-
Examples of old (ca. 1.0.0+) Rust code that still compiles?
Do you actually want to question all you know about Rust? Do this amazing quiz by the famed dtolnay.
-
[Media] Is the LinkedIn Rust quiz OK 🤨
If you want a correct and much harder Rust quiz, here you go.
-
Anything C can do Rust can do Better
⭐ Rust Quiz - David Tolnay
-
Carefully exploring Rust as a Python developer
One surprise perhaps is that both Python and C++ have multiple inheritance whereas Rust doesn't have implementation inheritance at all (Rust's traits can inherit but data structures and implementations cannot).
Both C++ and Rust have similar Quiz sites:
https://dtolnay.github.io/rust-quiz/
-
An interviewee has "(interest) Rust" in his resume, which question should I ask him ?
Obligatory: https://dtolnay.github.io/rust-quiz/
-
Rust (Programming Language) is now a skill that LinkedIn assesses
There is also this quiz
- Rust Quiz
What are some alternatives?
Rust-for-Linux - Adding support for the Rust language to the Linux kernel.
linkedin-skill-assessments-quizzes - Full reference of LinkedIn answers 2023 for skill assessments (aws-lambda, rest-api, javascript, react, git, html, jquery, mongodb, java, Go, python, machine-learning, power-point) linkedin excel test lösungen, linkedin machine learning test LinkedIn test questions and answers
rust - Empowering everyone to build reliable and efficient software.
cargo-llvm-lines - Count lines of LLVM IR per generic function
gccrs - GCC Front-End for Rust
db-dump - Library for scripting analyses against crates.io's database dumps
rust - Rust language bindings for TensorFlow
async-trait - Type erasure for async trait methods
rustc_codegen_gcc - libgccjit AOT codegen for rustc
rust-sokoban - Rust Sokoban book and code samples
rfcs - RFCs for changes to Rust
semver-trick - How to avoid complicated coordinated upgrades