bpaf
rustc-dev-guide
bpaf | rustc-dev-guide | |
---|---|---|
21 | 7 | |
315 | 1,580 | |
- | 1.4% | |
9.1 | 9.3 | |
6 days ago | 1 day ago | |
Rust | HTML | |
- | 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.
bpaf
- bpaf – Command line parser with applicative interface
-
Crate to print tables in CLI in a lazy fashion?
If you want to make smart decisions depending on widths of the cells - you have to consume the whole iterator to see what is the widest cell out there, it could be the last one for example. During that iteration you'll want either to store the values somehow or store preformatted bits in a string - something like this https://github.com/pacak/bpaf/blob/master/src/buffer.rs
- The Icculus Microgrant is giving out 250 dollar grants to open source projects, please brag about your project(s) in this thread so I can see them!
-
Announcing clap-markdown — automatically generate Markdown docs for clap command-line tools
bpaf does it here, giving access to primitives like "dump names of this parser" or "dump help for this subparser": https://github.com/pacak/bpaf/blob/semantic/src/docugen.rs
-
Branching based on the return type of a function/closure argument
https://github.com/pacak/bpaf/blob/master/src/from_os_str.rs - a concrete example
- cargo + dynamic shell completion = cauwugo
-
Yet another command line argument parser: bpaf 0.6.0
https://github.com/pacak/bpaf/issues/50 - I would appreciate some feedback from a new user on naming conventions used - there or here is fine.
-
Design comparison of clap and bpaf (arg parsers)
Most of the code change is here: https://github.com/pacak/bpaf/pull/57 https://github.com/pacak/bpaf/pull/60
-
Yet another command line argument parser: bpaf 0.5.5
Something like this, handles example from the ticket at least (sans hex digits) https://github.com/pacak/bpaf/blob/master/examples/sensors.rs
-
Yet another command line argument parser: bpaf 0.5.2
see https://github.com/pacak/bpaf/blob/rc-0.5.5/examples/custom_usage.rs
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.
What are some alternatives?
clap-rs - A full featured, fast Command Line Argument Parser for Rust
lang-team - Home of the Rust lang team
argparse-benchmarks-rs - Collected benchmarks for arg parsing crates written in Rust [Moved to: https://github.com/rosetta-rs/argparse-rosetta-rs]
sensible-env-logger - A pretty, sensible, easy-to-use logger for Rust.
cargo-supply-chain - Gather author, contributor and publisher data on crates in your dependency graph.
triagebot - Automation/tooling for Rust spaces
rust-argparse - The command-line argument parser library for rust
isahc - The practical HTTP client that is fun to use.
argparse-rosetta-rs - Comparing argparse APIs
MuOxi - MuOxi, a modern mud game engine written in Rust.
venial - "A very small syn"
Cargo - The Rust package manager