We have a whole working group this year focused on making the experience of writing CLIs awesome, so hopefully we’ll see even more great tools in the future!
I need to try implementing the string thing. It'd be a lot more fun to try to compete on speed if we were the same on accuracy.
Can you explain what you mean by this? Something like the people are going to focus on language and library features that help with writing CLIs? Or something else?
Asking because CLIs are one of my interests.
You can reach out to us on gitter [3].
[0]: https://github.com/rust-lang-nursery/cli-wg/issues
[1]: https://github.com/rust-clique/ and https://github.com/assert-rs/
[2]: https://rust-lang-nursery.github.io/cli-wg/index.html
[3]: https://gitter.im/rust-lang/WG-CLI
The areas we're trying to finish up for Rust 2018 Edition:
- Get clap (arg parsing) to 3.0 [4]
- Get assert_cmd [5] / assert_fs [6] to 1.0
- Finish work on man-page generation [7]
- Make it easier to package binaries [8] and document the CI for it [9]
[4]: https://github.com/rust-lang-nursery/cli-wg/issues/41
[5]: https://github.com/assert-rs/assert_cmd/
[6]: https://github.com/assert-rs/assert_fs
[7]: https://github.com/rust-lang-nursery/cli-wg/issues/38
Rust has different community working groups that focus on improving the Rust ecosystem in different ways this year: https://internals.rust-lang.org/t/announcing-the-2018-domain...
The TL;DR is that loc is faster by a few hundred milliseconds depending on repository size, but as cgag mentions doesn't have comment in string detection so can be quite off in its metrics, for example on the Rust repo Tokei says it has 643,754 lines of code where as loc says it's 635,849.
[0]: https://github.com/Aaronepower/tokei/blob/master/COMPARISON....