rustfmt
miri
Our great sponsors
rustfmt | miri | |
---|---|---|
57 | 120 | |
5,729 | 3,902 | |
1.3% | 2.3% | |
8.9 | 10.0 | |
8 days ago | 6 days ago | |
Rust | Rust | |
Apache License 2.0 | 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.
rustfmt
-
You can't do that because I hate you
The author provides very surface-level criticism of two Rust tools, but they don't look into why those choices were made.
With about five minutes of my time, I found out:
wrap_comments was introduced in 2019 [0]. There are bugs in the implementation (it breaks Markdown tables), so the option hasn't been marked as stable. Progress on the issue has been spotty.
--no-merge-sources is not trivial to re-implement [1]. The author has already explained why the flag no longer works -- Cargo integrated the command, but not all of the flags. This commit [2] explains why this functionality was removed in the first place.
Rust is open source, so the author of this blog post could improve the state of the software they care about by championing these issues. The --no-merge-sources error message even encourages you to open an issue, presumably so that the authors of Cargo can gauge the importance of certain flags/features.
You could even do something much simpler, like adding a comment to the related issues mentioning that you ran into these rough edges and that it made your life a little worse, or with a workaround that you found.
Alternatively, you can continue to write about how much free software sucks.
[0]: https://github.com/rust-lang/rustfmt/issues/3347
[1]: https://github.com/rust-lang/cargo/pull/10344
[2]: https://github.com/rust-lang/cargo/commit/3842d8e6f20067f716...
-
Let else will finally be formatted by rustfmt soon
The new style still supports single line let-else, and there is a configuration parameter to make it be on one line also for longer lines.
Yacin Tmimi for actually implementing the bloody thing
-
Is rustfmt abandoned? Will it ever format `let ... else` syntax?
I’m not sure they are? I don’t mean this to criticize anybody on the project — I’m sure they have other things going on — but there are a whole bunch of open PRs without even a single comment.
It seems there is an issue about this dating all the way back from 2018 but yet it still hasn't been fixed.
Presumably, https://github.com/rust-lang/rustfmt/pull/5690
-
Hey Rustaceans! Got a question? Ask here (22/2023)!
However since 4179 recent versions should merge configuration files. Not sure what the details / specifics are but if just ignoring the file entirely is not good enough you might give it its own directory and rustfmt.toml file and see if that works.
-
Rust Tips and Tricks #PartOne
Rustfmt is a tool that formats Rust code in compliance with style guidelines. Its name precisely reflects its purpose. To install rustfmt, you can run rustup component add rustfmt. Once installed, you can execute cargo fmt to format Rust code in your workspace. If you require further information, you can visit rustfmt’s GitHub repository.
-
What are some good practices when writing rust?
code must be formatted with rustfmt.
-
Hey Rustaceans! Got a question? Ask here (5/2023)!
Yes, some cases are not yet supported (https://github.com/rust-lang/rustfmt/issues/4914).
miri
-
RFC: Rust Has Provenance
Provenance is a dynamic property of pointer values. The actual underlying rules that a program must follow, even when using raw pointers and `unsafe`, are written in terms of provenance. Miri (https://github.com/rust-lang/miri) represents provenance as an actual value stored alongside each pointer's address, so it can check for violations of these rules.
Lifetimes are a static approximation of provenance. They are erased after being validated by the borrow checker, and do not exist in Miri or have any impact on what transformations the optimizer may perform. In other words, the provenance rules allow a superset of what the borrow checker allows.
- Mir: Strongly typed IR to implement fast and lightweight interpreters and JITs
- Erroneous UB Error with Miri?
-
I've incidentally created one of the fastest bounded MPSC queue
Actually, I've done more advanced tests with MIRI (see https://github.com/rust-lang/miri/issues/2920 for example) which allowed me to fix some issues. I've also made the code compatible with loom, but I didn't found the time yet to write and execute loom tests. That's on the TODO-list, and I need to track it with an issue too.
-
Interested in "secure programming languages", both theory and practice but mostly practice, where do I start?
He is one of the big brains behind Miri, which is a interpreter that runs on the MIR (compiler representation between human code and asm/machine code) and detects undefined behavior. Super useful tool for language safety, pretty interesting on its own.
-
Formal verification for unsafe code?
I would also run your tests in Miri (https://github.com/rust-lang/miri) to try to cover more bases.
-
Ouroboros is also unsound
You can run miri and it will tell you if the given run triggered any undefined behavior. It will not analyze it for every possible use of the code, but checking for the presence of this specific issue using it should be fairly simple.
-
From Stacks to Trees: A new aliasing model for Rust
If you do encounter a piece of code on which TB performs much worse than SB, do submit it as an issue! There was one recently and we massively improved TB performance on this case by improving garbage collection.
-
My Rust program (Well, game) is leaking memory, 4MB/s.
Have you tried adding miri checks to see specific warnings it suggests? It should have some memory leak checks aswell. https://github.com/rust-lang/miri
-
What would be your programming language of choice to implement a JIT compiler ?
Depends on what you mean by "better experience". What the article doesn't mention is the fact that you can still run into undefined behavior (including pointer aliasing) in C/C++/Zig and have your programs exhibit unexplainable weirdness, but you won't get any help from the language/compiler to figure out where it's coming from. In Rust you just run MIRI which tells you exactly where you have undefined behavior as long as you have at least one test which exercises the affected code path.
What are some alternatives?
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
rust-analyzer - A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer]
rust-analyzer - A Rust compiler front-end for IDEs
Rust for Visual Studio Code
vscode-rust
sublime-rust - The official Sublime Text 4 package for the Rust Programming Language
sanitizers - AddressSanitizer, ThreadSanitizer, MemorySanitizer
cons-list - Singly-linked list implementation in Rust
rust - Empowering everyone to build reliable and efficient software.
rust-on-raspberry-pi
CodeLLDB - A native debugger extension for VSCode based on LLDB
Helix - Native Ruby extensions without fear