I'm pretty new to Rust (lurking on the list for a while) but have been in the Haskell community for a while. While cabal in general is nothing that should be emulated, perhaps the Haskell hierarchy would be informative.
In Haskell, there are somewhat unofficial hierarchies, but here they are: prelude: http://hackage.haskell.org/packages/archive/base/4.6.0.1/doc/html/Prelude.html the "default" module that is included by default in all source files. base: http://hackage.haskell.org/package/base package that includes the prelude module and other core functionality. ghc libraries: http://www.haskell.org/ghc/docs/7.6.2/html/libraries/ ghc is the de facto reference implementation for haskell (queue flamewar) and includes a large set of libraries in addition to base haskell platform http://www.haskell.org/platform/changelog.html the "batteries included" distribution that includes many very commonly used libraries as a starting point for a new project On Tue, Apr 23, 2013 at 10:50 AM, Daniel Micay <danielmi...@gmail.com>wrote: > On Tue, Apr 23, 2013 at 1:06 PM, Graydon Hoare <gray...@mozilla.com> > wrote: > > Namely: > > > > - When we support static linking, will it be possible to link subsets > > of "the standard library" for space constrained devices? E.g. will > > we be able to compile it with section-per-function or such? > > Release builds could just be done with link-time optimization. It's > okay if it takes 5x as long and 3GiB of memory if it's just a single > build. Although I think there would have to be 3 versions of the > libraries (lto, static, dynamic). > _______________________________________________ > Rust-dev mailing list > Rust-dev@mozilla.org > https://mail.mozilla.org/listinfo/rust-dev >
_______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
