Considering the content of the current libstd, I think "util" is indeed an appropriate name for this module.
Some other propositions : - "base" - "rust" - "platform" - "stock" > Maybe it is from spending too much time with java, but I tend to name those > kind of libs `util`, > because often what they are is adding extra functionality to the standard > library. > > In order for it to be really useful, though, I think that its role needs to > be clearly defined > (as below), and that definition adhered to. I really like the haskell package > idea, but only if > there is a lighter-weight default as well. > >> It's not for experimental stuff. Let me clarify the role we're >> discussing. The "ext" library, for lack of a better name, will: >> >> - Be a library hosted in a mozilla and/or rust-lang.org repo >> - That _just re-exports_ (pub extern mod's) a bunch of packages >> - Each of which is: >> - Developed independently in their own repos >> - By their own contributor communities >> - At their own pace >> - Applying some editorial standards to the selected packages >> - And supporting them version-to-version even if they bitrot >> or radically change upstream _______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
