argh
rust-prehistory
Our great sponsors
| argh | rust-prehistory | |
|---|---|---|
| 7 | 18 | |
| 1,568 | 566 | |
| 2.3% | - | |
| 6.0 | 0.8 | |
| 16 days ago | 12 months ago | |
| Rust | C | |
| BSD 3-clause "New" or "Revised" License | GNU General Public License v3.0 or later |
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.
argh
-
Crate List - Blessed.rs
https://github.com/google/argh is another minimal library for CLI argument parsing that could be in the list
-
Rust Web Framework Comparison
My go-to is argh[1], as it's more lightweight while still providing a nice derive-based API.
[1]: https://github.com/google/argh
-
Immediately off the top of your head what is the best Rust CLI library.
It'll panic if the path contains non-UTF8-able bytes.
-
fncmd: Command line interface as a function.
Yes clap needs a lot of boilerplate that small programs don't always need, but if you're going to simplify it, I don't think having a bunch of arguments given to the main function is better than having an option struct as in argh. Such an option struct can be given to other functions from the main, can have dedicated consistency check or completion methods, etc.
-
Newbie frustration: can we KISS more?
Typically programs are configured through a config object. People like to use things like clap, structopt, or argh for passing in arguments through the CLI https://github.com/google/argh. You can also use the env! macro for embedding values in at compile time, or by going through the std::env::var infrastructure for runtime env vars.
-
Darkroom: A VCR contract testing tool built in Rust
Until the argh crate bumps their version I cannot updater the version on crates.io so the install command currently is: cargo install --git https://github.com/mkatychev/darkroom
-
Announcement: xflags, fast-to-compile proc macro for cli args
Ahh. The secondary reason I discounted Argh as "unsuitable for purpose" after "Doesn't support using OsString under the hood".
rust-prehistory
-
Did Rust ever have breaking syntax changes?
There’s a rust-prehistory repo preserving Rust’s compiler code at very early stage. You can see how Rust looks like at that time.
-
What should be included in a history of the Rust language?
https://github.com/graydon/rust-prehistory is another good resource, particularly the doc/notes directory. All kinds of good stuff in there that looks pretty different than today. I also liked Marijn's talk, The Rust That Could Have Been.
-
Is there somewhere I can view the history of rust before 1.0?
There's also this repository depending how far back you want
-
How to Learn Modern Rust
If, on the other hand, you’re interested in pre-modern Rust, there’s always this repo: https://github.com/graydon/rust-prehistory
-
Array type annotation syntax: String[] -vs- [String]
For some snapshots on the history of the language up to 1.0 check out: https://brson.github.io/archaea/. For some really ancient stuff check out the graydon/rust-prehistory/ repo. Also looking at the oldest commits and issues on the Rust repo can be pretty interesting. It's a great public resource.
- Rust Prehistory Repo
-
Happy 12th Birthday, Rust
As Graydon Hoare notes in the comments on GitHub this wasn't the first repo so the real history goes back even further. He's also shared a "prehistory" repo [1] which is interesting to browse. The first commit [2] in _that_ repo is from 2008 but Graydon mentions starting work back in 2006.
Anyway in a sense this repo represents Rust in the real world rather than in gestation, so seems apt to call it the birthday.
[1] https://github.com/graydon/rust-prehistory
[2] https://github.com/graydon/rust-prehistory/commit/1969e085e3...
-
I created my own programming language that compiles into Lua code but uses a more C/Rust like syntax
Early Rust was very different (example). It is almost certain that modern Rust took a lot of cues from Go. And, as above, Go was obviously heavily inspired by C, just like your language. So, all told, where you landed is likely very much what is expected.
-
How is Rust written with Rust?
The pre-git history was imported as https://github.com/graydon/rust-prehistory
-
Graydon Hoare: “Rust didn't start ”as a research project at Mozilla in 2010“
Two other links related to ancient Rust:
* https://github.com/graydon/rust-prehistory -> the code from before the rust-lang/rust repo
* https://youtube.com/watch?v=79PSagCD_AY -> a talk I gave around the 1.0 release giving my personal perspective on the history.
Oh heck, one more fun one: https://github.com/brson/archaea
What are some alternatives?
clap-rs - A full featured, fast Command Line Argument Parser for Rust
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
structopt - Parse command line arguments by defining a struct.
nannou - A Creative Coding Framework for Rust.
hello-actix - Hello, actix!
racket - The Racket repository
xflags
crater - Run experiments across parts of the Rust ecosystem!
argparse-benchmarks-rs - Collected benchmarks for arg parsing crates written in Rust [Moved to: https://github.com/rosetta-rs/argparse-rosetta-rs]
compiler-benchmark - Benchmarks compilation speeds of different combinations of languages and compilers.
pico-args - An ultra simple CLI arguments parser.
nelua-lang - Minimal, efficient, statically-typed and meta-programmable systems programming language heavily inspired by Lua, which compiles to C and native code.