Our great sponsors
rr | rustfmt | |
---|---|---|
98 | 57 | |
8,556 | 5,710 | |
1.1% | 1.9% | |
9.6 | 8.9 | |
7 days ago | 1 day ago | |
C++ | Rust | |
GNU General Public License v3.0 or later | 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.
rr
-
So you think you want to write a deterministic hypervisor?
https://rr-project.org/ had the same problem. They use the retired conditional branch counter instead of instruction counter, and then instruction steeping until at the correct address.
-
Is Something Bugging You?
That'll work great for your Distributed QSort Incorporated startup, where the only product is a sorting algorithm.
Formal software verification is very useful. But what can be usefully formalized is rather limited, and what can be formalized correctly in practice is even more limited. That means you need to restrict your scope to something sane and useful. As a result, in the real world running thousands of tests is practically useful. (Well, it depends on what those tests are; it's easy to write 1000s of tests that either test the same thing, or only test the things that will pass and not the things that would fail.) They are especially useful if running in a mode where the unexpected happens often, as it sounds like this system can do. (It's reminiscent of rr's chaos mode -- https://rr-project.org/ linking to https://robert.ocallahan.org/2016/02/introducing-rr-chaos-mo... )
-
When "letting it crash" is not enough
The approach of check-pointing computation such that it is resumable and restartable sounds similar to a time-traveling debugger, like rr or WinDbg:
https://learn.microsoft.com/windows-hardware/drivers/debugge...
-
When I got started I debugged using printf() today I debug with print()
https://rr-project.org
This is indeed a problem people have with debuggers, so some very smart people found a way to fix it.
...and you're not on Linux, because on Linux we have rr! https://rr-project.org/
(I still use print statements 99.99% of the time though)
- OpenBSD KDE Plasma Desktop
-
Firefox 118
> I've heard Linux support was down to like one guy [...]
Linux support is down to you. It's down to all of us. Install rr (https://rr-project.org/) and capture a crash with it.
Then you can replay the crash, find out that it's actually crashing in your closed-source graphics driver, which will motivate you to switch to an open source driver and fix your issue.
Also, while you're at it, update your linux kernel and wayland. They've both had bugs that could manifest as random firefox crashes in the last several months.
- A Modern C Development Environment
-
Raku: A Language for Gremlins
I imagine you are referring to https://rr-project.org/ ?
Had never heard of it, looks pretty amazing, I might actually enjoy debugging now!
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).
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
rust-on-raspberry-pi
CodeLLDB - A native debugger extension for VSCode based on LLDB
gef - GEF (GDB Enhanced Features) - a modern experience for GDB with advanced debugging capabilities for exploit devs & reverse engineers on Linux
rrweb - record and replay the web
Module Linker - browse modules by clicking directly on "import" statements on GitHub