I made some metadata changes. Let's see if you agree with them.
Remove "heavily WIP" from description. This crate has been around for a long time now and is used a lot. The API is already very usable and handy. Just because there will be more breaking releases does not mean the entire crate is in some early work in progress state IMO. A bit more cleanup and API fixes and I rather think we should go 1.0. Such a fundamental library should be able to be "stable". Which in turn does not mean there can never be a 2.0, just that it's ready for general use. Which this already is, by far.
Add cidr keyword.
Remove "os" category. The description of that category on crates.io is "Bindings to operating system-specific APIs.". This crate does not bind to/call any OS APIs.
Add "parser-implementation" category. Since this crate implements parsing a specific format (cidr).
I made some metadata changes. Let's see if you agree with them.
Remove "heavily WIP" from description. This crate has been around for a long time now and is used a lot. The API is already very usable and handy. Just because there will be more breaking releases does not mean the entire crate is in some early work in progress state IMO. A bit more cleanup and API fixes and I rather think we should go 1.0. Such a fundamental library should be able to be "stable". Which in turn does not mean there can never be a 2.0, just that it's ready for general use. Which this already is, by far.
Add
cidrkeyword.Remove "os" category. The description of that category on crates.io is "Bindings to operating system-specific APIs.". This crate does not bind to/call any OS APIs.
Add "parser-implementation" category. Since this crate implements parsing a specific format (cidr).