You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ZeroVer's patent-pending zero-based versioning
scheme can obviously be used by everyone, but not every usage is
necessarily notable. Check that the first and at least one other
criterion apply:
A current ZeroVer-compliant version (0.*) or long history of ZeroVer usage, and
Very wide exposure (i.e., 1,000+ GitHub stars), or
Active promotion as part of a paid product or service (e.g., Hashicorp Vault), or
Relative maturity and infrastructural importance (e.g., Compiz, docutils)
Additional notability info
libc is one of the most popular libraries for Rust programming language providing bindings to platforms' system libraries. It is depended on by 39,123 crates. A release of libc 0.2.0 in 2015 (back when the language was much smaller) caused an event known as "libcpocalyse" causing a lot of crates to break due to incompatible type definitions (structures defined in different versions of crates are different) - for example, Servo had to coordinate upgrading 52 dependencies.
The library is so popular at this point that releasing 1.0 is tricky as doing so could break everything: rust-lang/libc#547.
Citation info
The text was updated successfully, but these errors were encountered:
Basic info
Project name: libc
Project link: https://github.com/rust-lang/libc
Qualifications
ZeroVer's patent-pending zero-based versioning
scheme can obviously be used by everyone, but not every usage is
necessarily notable. Check that the first and at least one other
criterion apply:
0.*
) or long history of ZeroVer usage, andAdditional notability info
libc
is one of the most popular libraries for Rust programming language providing bindings to platforms' system libraries. It is depended on by 39,123 crates. A release of libc 0.2.0 in 2015 (back when the language was much smaller) caused an event known as "libcpocalyse" causing a lot of crates to break due to incompatible type definitions (structures defined in different versions of crates are different) - for example, Servo had to coordinate upgrading 52 dependencies.The library is so popular at this point that releasing 1.0 is tricky as doing so could break everything: rust-lang/libc#547.
Citation info
The text was updated successfully, but these errors were encountered: