namespacing-rfc
nakala
| namespacing-rfc | nakala | |
|---|---|---|
| 6 | 3 | |
| 47 | 45 | |
| - | - | |
| 3.5 | 0.0 | |
| 10 months ago | over 3 years ago | |
| Rust | ||
| - | The Unlicense |
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.
namespacing-rfc
-
Why so many basic features are not part of the standard library?
An RFC for packages as optional namespaces is still open. An implementation of it exists, but might need an older toolchain to build today.
-
AWS SDK for Rust enters developer preview
There is work going on to allow crate namespacing (foo/bar): https://github.com/Manishearth/namespacing-rfc/blob/main/000...
- How can we make sure this doesn't happen with Crates.io?
-
Crates.io namespaces
A prototype exists for this https://github.com/Manishearth/namespacing-rfc/issues/10
-
Recent crates on docs.rs :(
namespaces have not been ruled out, I have a pre-RFC and there's even a prototype implementation out there
nakala
- Nakala
-
RFC: Add ngram indexing support to ripgrep (2020)
Author of ripgrep here.
I'm not sure if this is ever going to happen. I did make some progress in the initial design here (warning, very long): https://github.com/BurntSushi/nakala/blob/15d55b742c07a26944...
But... I was not extremely confident in my design, and proving it out will likely take at least months of continuous work. I don't quite have that kind of time at the moment, and I ended up diverting to work on Rust's regex crate rewrite.
Perhaps I'll revisit this idea some day, but probably not any time soon unfortunately.
-
Recent crates on docs.rs :(
The nuance here is that I had a good faith intention of using that name to develop a usable crate for use in other projects. But did I really? How can you know? And even if I did have a good faith intention, who's to say that I'll follow through? I haven't followed through on nakala yet, although I'm working on it. I hope to stop "squatting" it some day. But maybe I won't. I dunno.
What are some alternatives?
wg - Coordination repository for the Secure Code Working Group
rust-notes - Terse Rust learning material. :crab:
compiler-team - A home for compiler team planning documents, meeting minutes, and other such things.
crates.io - The Rust package registry
rustsec - RustSec API & Tooling
libs-team - The home of the library team
rfcs - RFCs for changes to Rust
ua-parser-js - UAParser.js - Free & open-source JavaScript library to detect user's Browser, Engine, OS, CPU, and Device type/model. Runs either in browser (client-side) or node.js (server-side).
docs.rs - crates.io documentation generator
cargo-crev - A cryptographically verifiable code review system for the cargo (Rust) package manager.