rustc-dev-guide
issuewhiz
rustc-dev-guide | issuewhiz | |
---|---|---|
7 | 2 | |
1,579 | 3 | |
1.3% | - | |
9.3 | 7.9 | |
9 days ago | 6 months ago | |
HTML | JavaScript | |
Apache License 2.0 | GNU Affero General Public License v3.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.
rustc-dev-guide
-
The rust project has a burnout problem
yes, it's possible! that list doesn't exist today but i would love to create it. i wrote a draft a few years ago before shifting to other work; someone recently expressed interest in reviving that project: https://github.com/rust-lang/rustc-dev-guide/pull/1463
<3 i'm glad you enjoyed it
-
How Rust transforms into Machine Code.
It's possible - you could open an issue on the rustc-dev-guide repo if you'd like. https://github.com/rust-lang/rustc-dev-guide/
-
Accessible Documentation?
I'm very confident that this would be well received! I'm not sure where the source code for rustdoc lives, but I know that the internals getting started guide is here: https://github.com/rust-lang/rustc-dev-guide/blob/master/src/rustdoc.md. That would be a good place to start if you're looking into how the HTML is generated.
-
Yet another command line argument parser: bpaf 0.5.5
Do you have links to any good info about how much rustc reuses from previous runs? This is the first time i hear about reuse at the function level. I guess the rustc-dev-guide would be a good place for me to start?
-
Discussion Thread
Inspired by the rust compiler, you could represent the entire state of the application as a graph of operations with inputs and outputs. You can hash all the inputs and use that to memoize the operations, so that you don't have to repeat them, you can cache them in memory or on disk, and it helps you track which parts of the app state actually change between user operations and you can then be sure you put all the changes in the undo/redo stack, and so that you don't have to store duplicate copies of things that don't change. (How's that for a run-on sentence?) You could run a general binary diff algorithm between subsequent versions of the same operation with different inputs to try to reduce the memory used by storing the different versions, and have specialized diff algorithms for specific types of data. (How do you identify related operations? How much CPU does this use?) You can have a background task that compresses older versions with LZ4 or zstd. You can have a background task that saves older versions on-disk when there's memory pressure.
-
What’s everyone working on this week (11/2022)?
I contributed a couple small bugfixes for issues I ran into along the way as well. 1, 2
-
Best practices for writing code comments
It's rustdoc: https://github.com/rust-lang/rustc-dev-guide/blob/master/src...
> Rustdoc actually uses the rustc internals directly. It lives in-tree with the compiler and standard library. This chapter is about how it works. For information about Rustdoc's features and how to use them, see the Rustdoc book. For more details about how rustdoc works, see the "Rustdoc internals" chapter.
issuewhiz
-
The rust project has a burnout problem
A few guidelines to avoid maintainer's burnout:
* Do not allow questions on GitHub issues, it's a poor place for conversations. I find Discourse or some other forum (or mailing list) a better place to do that, which allows community participation (and you can automate moderation using something like https://github.com/pierotofy/issuewhiz)
* People owe you nothing, just as you owe them nothing; you don't have to fix an issue or merge a pull request because somebody opened one.
* Try review and merge contributions, but on your own timeframe. If people have urgency, kindly invite them to get a paid support agreement.
* Don't engage in quarrels; you always have the option to ignore or ban the offenders.
* Document FAQs.
- Show HN: IssueWhiz – Automated Issue Triaging
What are some alternatives?
lang-team - Home of the Rust lang team
bpaf - Command line parser with applicative interface
sensible-env-logger - A pretty, sensible, easy-to-use logger for Rust.
triagebot - Automation/tooling for Rust spaces
isahc - The practical HTTP client that is fun to use.
MuOxi - MuOxi, a modern mud game engine written in Rust.
Cargo - The Rust package manager
venial - "A very small syn"
argparse-rosetta-rs - Comparing argparse APIs
rustic - Rust development environment for Emacs
rust - Empowering everyone to build reliable and efficient software.
Crafting Interpreters - Repository for the book "Crafting Interpreters"