2014-01-25 04:27:22 +01:00
|
|
|
# Copyright 2014 The Rust Project Developers. See the COPYRIGHT
|
|
|
|
# file at the top-level directory of this distribution and at
|
|
|
|
# http://rust-lang.org/COPYRIGHT.
|
|
|
|
#
|
|
|
|
# Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or
|
|
|
|
# http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
|
|
|
|
# <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your
|
|
|
|
# option. This file may not be copied, modified, or distributed
|
|
|
|
# except according to those terms.
|
|
|
|
|
|
|
|
################################################################################
|
|
|
|
# Rust's standard distribution of crates and tools
|
|
|
|
#
|
|
|
|
# The crates outlined below are the standard distribution of libraries provided
|
|
|
|
# in a rust installation. These rules are meant to abstract over the
|
|
|
|
# dependencies (both native and rust) of crates and basically generate all the
|
|
|
|
# necessary makefile rules necessary to build everything.
|
|
|
|
#
|
|
|
|
# Here's an explanation of the variables below
|
|
|
|
#
|
|
|
|
# TARGET_CRATES
|
|
|
|
# This list of crates will be built for all targets, including
|
|
|
|
# cross-compiled targets
|
|
|
|
#
|
|
|
|
# HOST_CRATES
|
|
|
|
# This list of crates will be compiled for only host targets. Note that
|
|
|
|
# this set is explicitly *not* a subset of TARGET_CRATES, but rather it is
|
|
|
|
# a disjoint set. Nothing in the TARGET_CRATES set can depend on crates in
|
|
|
|
# the HOST_CRATES set, but the HOST_CRATES set can depend on target
|
|
|
|
# crates.
|
|
|
|
#
|
|
|
|
# TOOLS
|
|
|
|
# A list of all tools which will be built as part of the compilation
|
|
|
|
# process. It is currently assumed that most tools are built through
|
|
|
|
# src/driver/driver.rs with a particular configuration (there's a
|
|
|
|
# corresponding library providing the implementation)
|
|
|
|
#
|
|
|
|
# DEPS_<crate>
|
|
|
|
# These lists are the dependencies of the <crate> that is to be built.
|
2014-11-14 23:38:41 +01:00
|
|
|
# Rust dependencies are listed bare (i.e. std) and native
|
2014-05-03 02:56:35 +02:00
|
|
|
# dependencies have a "native:" prefix (i.e. native:hoedown). All deps
|
2014-01-25 04:27:22 +01:00
|
|
|
# will be built before the crate itself is built.
|
|
|
|
#
|
|
|
|
# TOOL_DEPS_<tool>/TOOL_SOURCE_<tool>
|
|
|
|
# Similar to the DEPS variable, this is the library crate dependencies
|
|
|
|
# list for tool as well as the source file for the specified tool
|
|
|
|
#
|
|
|
|
# You shouldn't need to modify much other than these variables. Crates are
|
|
|
|
# automatically generated for all stage/host/target combinations.
|
|
|
|
################################################################################
|
|
|
|
|
2014-11-14 23:38:41 +01:00
|
|
|
TARGET_CRATES := libc std flate arena term \
|
2015-01-02 08:53:35 +01:00
|
|
|
serialize getopts collections test rand \
|
2015-01-20 19:45:29 +01:00
|
|
|
log graphviz core rbml alloc \
|
2015-06-25 19:07:01 +02:00
|
|
|
rustc_unicode rustc_bitflags \
|
|
|
|
alloc_system
|
2014-12-18 23:46:26 +01:00
|
|
|
RUSTC_CRATES := rustc rustc_typeck rustc_borrowck rustc_resolve rustc_driver \
|
2015-04-07 12:10:53 +02:00
|
|
|
rustc_trans rustc_back rustc_llvm rustc_privacy rustc_lint \
|
2015-07-31 09:04:06 +02:00
|
|
|
rustc_data_structures rustc_front rustc_platform_intrinsics
|
2015-01-02 08:53:35 +01:00
|
|
|
HOST_CRATES := syntax $(RUSTC_CRATES) rustdoc fmt_macros
|
2015-05-03 02:57:41 +02:00
|
|
|
TOOLS := compiletest rustdoc rustc rustbook error-index-generator
|
2014-01-25 04:27:22 +01:00
|
|
|
|
2014-05-01 05:05:14 +02:00
|
|
|
DEPS_core :=
|
2014-09-23 02:12:15 +02:00
|
|
|
DEPS_libc := core
|
deprecate Unicode functions that will be moved to crates.io
This patch
1. renames libunicode to librustc_unicode,
2. deprecates several pieces of libunicode (see below), and
3. removes references to deprecated functions from
librustc_driver and libsyntax. This may change pretty-printed
output from these modules in cases involving wide or combining
characters used in filenames, identifiers, etc.
The following functions are marked deprecated:
1. char.width() and str.width():
--> use unicode-width crate
2. str.graphemes() and str.grapheme_indices():
--> use unicode-segmentation crate
3. str.nfd_chars(), str.nfkd_chars(), str.nfc_chars(), str.nfkc_chars(),
char.compose(), char.decompose_canonical(), char.decompose_compatible(),
char.canonical_combining_class():
--> use unicode-normalization crate
2015-04-14 21:52:37 +02:00
|
|
|
DEPS_rustc_unicode := core
|
2015-06-25 19:07:01 +02:00
|
|
|
DEPS_alloc := core libc alloc_system
|
deprecate Unicode functions that will be moved to crates.io
This patch
1. renames libunicode to librustc_unicode,
2. deprecates several pieces of libunicode (see below), and
3. removes references to deprecated functions from
librustc_driver and libsyntax. This may change pretty-printed
output from these modules in cases involving wide or combining
characters used in filenames, identifiers, etc.
The following functions are marked deprecated:
1. char.width() and str.width():
--> use unicode-width crate
2. str.graphemes() and str.grapheme_indices():
--> use unicode-segmentation crate
3. str.nfd_chars(), str.nfkd_chars(), str.nfc_chars(), str.nfkc_chars(),
char.compose(), char.decompose_canonical(), char.decompose_compatible(),
char.canonical_combining_class():
--> use unicode-normalization crate
2015-04-14 21:52:37 +02:00
|
|
|
DEPS_std := core libc rand alloc collections rustc_unicode \
|
2015-07-27 22:41:35 +02:00
|
|
|
native:rust_builtin native:backtrace \
|
2015-06-25 19:07:01 +02:00
|
|
|
alloc_system
|
2014-04-17 21:00:08 +02:00
|
|
|
DEPS_graphviz := std
|
2015-06-25 19:07:01 +02:00
|
|
|
DEPS_syntax := std term serialize log fmt_macros arena libc rustc_bitflags
|
2014-12-05 20:17:35 +01:00
|
|
|
DEPS_rustc_driver := arena flate getopts graphviz libc rustc rustc_back rustc_borrowck \
|
2015-01-15 19:47:17 +01:00
|
|
|
rustc_typeck rustc_resolve log syntax serialize rustc_llvm \
|
2015-07-31 09:04:06 +02:00
|
|
|
rustc_trans rustc_privacy rustc_lint rustc_front
|
2015-01-15 19:47:17 +01:00
|
|
|
|
2014-11-26 12:11:29 +01:00
|
|
|
DEPS_rustc_trans := arena flate getopts graphviz libc rustc rustc_back \
|
2015-07-31 09:04:06 +02:00
|
|
|
log syntax serialize rustc_llvm rustc_front rustc_platform_intrinsics
|
|
|
|
DEPS_rustc_typeck := rustc syntax rustc_front rustc_platform_intrinsics
|
|
|
|
DEPS_rustc_borrowck := rustc rustc_front log graphviz syntax
|
|
|
|
DEPS_rustc_resolve := rustc rustc_front log syntax
|
|
|
|
DEPS_rustc_privacy := rustc rustc_front log syntax
|
2015-02-25 12:44:44 +01:00
|
|
|
DEPS_rustc_lint := rustc log syntax
|
2014-07-30 02:06:37 +02:00
|
|
|
DEPS_rustc := syntax flate arena serialize getopts rbml \
|
2015-04-07 12:10:53 +02:00
|
|
|
log graphviz rustc_llvm rustc_back rustc_data_structures
|
2015-06-25 19:07:01 +02:00
|
|
|
DEPS_rustc_llvm := native:rustllvm libc std rustc_bitflags
|
2015-07-17 01:46:36 +02:00
|
|
|
DEPS_rustc_platform_intrinsics := rustc rustc_llvm
|
2015-07-31 09:04:06 +02:00
|
|
|
DEPS_rustc_back := std syntax rustc_llvm rustc_front flate log libc
|
|
|
|
DEPS_rustc_front := std syntax log serialize
|
2015-04-07 12:10:53 +02:00
|
|
|
DEPS_rustc_data_structures := std log serialize
|
2014-11-27 15:57:47 +01:00
|
|
|
DEPS_rustdoc := rustc rustc_driver native:hoedown serialize getopts \
|
2015-07-31 09:04:06 +02:00
|
|
|
test rustc_lint rustc_front
|
2015-01-16 21:20:03 +01:00
|
|
|
DEPS_rustc_bitflags := core
|
2014-03-14 19:16:10 +01:00
|
|
|
DEPS_flate := std native:miniz
|
std: Recreate a `collections` module
As with the previous commit with `librand`, this commit shuffles around some
`collections` code. The new state of the world is similar to that of librand:
* The libcollections crate now only depends on libcore and liballoc.
* The standard library has a new module, `std::collections`. All functionality
of libcollections is reexported through this module.
I would like to stress that this change is purely cosmetic. There are very few
alterations to these primitives.
There are a number of notable points about the new organization:
* std::{str, slice, string, vec} all moved to libcollections. There is no reason
that these primitives shouldn't be necessarily usable in a freestanding
context that has allocation. These are all reexported in their usual places in
the standard library.
* The `hashmap`, and transitively the `lru_cache`, modules no longer reside in
`libcollections`, but rather in libstd. The reason for this is because the
`HashMap::new` contructor requires access to the OSRng for initially seeding
the hash map. Beyond this requirement, there is no reason that the hashmap
could not move to libcollections.
I do, however, have a plan to move the hash map to the collections module. The
`HashMap::new` function could be altered to require that the `H` hasher
parameter ascribe to the `Default` trait, allowing the entire `hashmap` module
to live in libcollections. The key idea would be that the default hasher would
be different in libstd. Something along the lines of:
// src/libstd/collections/mod.rs
pub type HashMap<K, V, H = RandomizedSipHasher> =
core_collections::HashMap<K, V, H>;
This is not possible today because you cannot invoke static methods through
type aliases. If we modified the compiler, however, to allow invocation of
static methods through type aliases, then this type definition would
essentially be switching the default hasher from `SipHasher` in libcollections
to a libstd-defined `RandomizedSipHasher` type. This type's `Default`
implementation would randomly seed the `SipHasher` instance, and otherwise
perform the same as `SipHasher`.
This future state doesn't seem incredibly far off, but until that time comes,
the hashmap module will live in libstd to not compromise on functionality.
* In preparation for the hashmap moving to libcollections, the `hash` module has
moved from libstd to libcollections. A previously snapshotted commit enables a
distinct `Writer` trait to live in the `hash` module which `Hash`
implementations are now parameterized over.
Due to using a custom trait, the `SipHasher` implementation has lost its
specialized methods for writing integers. These can be re-added
backwards-compatibly in the future via default methods if necessary, but the
FNV hashing should satisfy much of the need for speedier hashing.
A list of breaking changes:
* HashMap::{get, get_mut} no longer fails with the key formatted into the error
message with `{:?}`, instead, a generic message is printed. With backtraces,
it should still be not-too-hard to track down errors.
* The HashMap, HashSet, and LruCache types are now available through
std::collections instead of the collections crate.
* Manual implementations of hash should be parameterized over `hash::Writer`
instead of just `Writer`.
[breaking-change]
2014-05-30 03:50:12 +02:00
|
|
|
DEPS_arena := std
|
2014-04-25 19:10:03 +02:00
|
|
|
DEPS_graphviz := std
|
2014-01-29 03:51:33 +01:00
|
|
|
DEPS_glob := std
|
std: Recreate a `collections` module
As with the previous commit with `librand`, this commit shuffles around some
`collections` code. The new state of the world is similar to that of librand:
* The libcollections crate now only depends on libcore and liballoc.
* The standard library has a new module, `std::collections`. All functionality
of libcollections is reexported through this module.
I would like to stress that this change is purely cosmetic. There are very few
alterations to these primitives.
There are a number of notable points about the new organization:
* std::{str, slice, string, vec} all moved to libcollections. There is no reason
that these primitives shouldn't be necessarily usable in a freestanding
context that has allocation. These are all reexported in their usual places in
the standard library.
* The `hashmap`, and transitively the `lru_cache`, modules no longer reside in
`libcollections`, but rather in libstd. The reason for this is because the
`HashMap::new` contructor requires access to the OSRng for initially seeding
the hash map. Beyond this requirement, there is no reason that the hashmap
could not move to libcollections.
I do, however, have a plan to move the hash map to the collections module. The
`HashMap::new` function could be altered to require that the `H` hasher
parameter ascribe to the `Default` trait, allowing the entire `hashmap` module
to live in libcollections. The key idea would be that the default hasher would
be different in libstd. Something along the lines of:
// src/libstd/collections/mod.rs
pub type HashMap<K, V, H = RandomizedSipHasher> =
core_collections::HashMap<K, V, H>;
This is not possible today because you cannot invoke static methods through
type aliases. If we modified the compiler, however, to allow invocation of
static methods through type aliases, then this type definition would
essentially be switching the default hasher from `SipHasher` in libcollections
to a libstd-defined `RandomizedSipHasher` type. This type's `Default`
implementation would randomly seed the `SipHasher` instance, and otherwise
perform the same as `SipHasher`.
This future state doesn't seem incredibly far off, but until that time comes,
the hashmap module will live in libstd to not compromise on functionality.
* In preparation for the hashmap moving to libcollections, the `hash` module has
moved from libstd to libcollections. A previously snapshotted commit enables a
distinct `Writer` trait to live in the `hash` module which `Hash`
implementations are now parameterized over.
Due to using a custom trait, the `SipHasher` implementation has lost its
specialized methods for writing integers. These can be re-added
backwards-compatibly in the future via default methods if necessary, but the
FNV hashing should satisfy much of the need for speedier hashing.
A list of breaking changes:
* HashMap::{get, get_mut} no longer fails with the key formatted into the error
message with `{:?}`, instead, a generic message is printed. With backtraces,
it should still be not-too-hard to track down errors.
* The HashMap, HashSet, and LruCache types are now available through
std::collections instead of the collections crate.
* Manual implementations of hash should be parameterized over `hash::Writer`
instead of just `Writer`.
[breaking-change]
2014-05-30 03:50:12 +02:00
|
|
|
DEPS_serialize := std log
|
2014-07-30 02:06:37 +02:00
|
|
|
DEPS_rbml := std log serialize
|
std: Recreate a `collections` module
As with the previous commit with `librand`, this commit shuffles around some
`collections` code. The new state of the world is similar to that of librand:
* The libcollections crate now only depends on libcore and liballoc.
* The standard library has a new module, `std::collections`. All functionality
of libcollections is reexported through this module.
I would like to stress that this change is purely cosmetic. There are very few
alterations to these primitives.
There are a number of notable points about the new organization:
* std::{str, slice, string, vec} all moved to libcollections. There is no reason
that these primitives shouldn't be necessarily usable in a freestanding
context that has allocation. These are all reexported in their usual places in
the standard library.
* The `hashmap`, and transitively the `lru_cache`, modules no longer reside in
`libcollections`, but rather in libstd. The reason for this is because the
`HashMap::new` contructor requires access to the OSRng for initially seeding
the hash map. Beyond this requirement, there is no reason that the hashmap
could not move to libcollections.
I do, however, have a plan to move the hash map to the collections module. The
`HashMap::new` function could be altered to require that the `H` hasher
parameter ascribe to the `Default` trait, allowing the entire `hashmap` module
to live in libcollections. The key idea would be that the default hasher would
be different in libstd. Something along the lines of:
// src/libstd/collections/mod.rs
pub type HashMap<K, V, H = RandomizedSipHasher> =
core_collections::HashMap<K, V, H>;
This is not possible today because you cannot invoke static methods through
type aliases. If we modified the compiler, however, to allow invocation of
static methods through type aliases, then this type definition would
essentially be switching the default hasher from `SipHasher` in libcollections
to a libstd-defined `RandomizedSipHasher` type. This type's `Default`
implementation would randomly seed the `SipHasher` instance, and otherwise
perform the same as `SipHasher`.
This future state doesn't seem incredibly far off, but until that time comes,
the hashmap module will live in libstd to not compromise on functionality.
* In preparation for the hashmap moving to libcollections, the `hash` module has
moved from libstd to libcollections. A previously snapshotted commit enables a
distinct `Writer` trait to live in the `hash` module which `Hash`
implementations are now parameterized over.
Due to using a custom trait, the `SipHasher` implementation has lost its
specialized methods for writing integers. These can be re-added
backwards-compatibly in the future via default methods if necessary, but the
FNV hashing should satisfy much of the need for speedier hashing.
A list of breaking changes:
* HashMap::{get, get_mut} no longer fails with the key formatted into the error
message with `{:?}`, instead, a generic message is printed. With backtraces,
it should still be not-too-hard to track down errors.
* The HashMap, HashSet, and LruCache types are now available through
std::collections instead of the collections crate.
* Manual implementations of hash should be parameterized over `hash::Writer`
instead of just `Writer`.
[breaking-change]
2014-05-30 03:50:12 +02:00
|
|
|
DEPS_term := std log
|
2014-02-03 00:20:32 +01:00
|
|
|
DEPS_getopts := std
|
deprecate Unicode functions that will be moved to crates.io
This patch
1. renames libunicode to librustc_unicode,
2. deprecates several pieces of libunicode (see below), and
3. removes references to deprecated functions from
librustc_driver and libsyntax. This may change pretty-printed
output from these modules in cases involving wide or combining
characters used in filenames, identifiers, etc.
The following functions are marked deprecated:
1. char.width() and str.width():
--> use unicode-width crate
2. str.graphemes() and str.grapheme_indices():
--> use unicode-segmentation crate
3. str.nfd_chars(), str.nfkd_chars(), str.nfc_chars(), str.nfkc_chars(),
char.compose(), char.decompose_canonical(), char.decompose_compatible(),
char.canonical_combining_class():
--> use unicode-normalization crate
2015-04-14 21:52:37 +02:00
|
|
|
DEPS_collections := core alloc rustc_unicode
|
std: Recreate a `rand` module
This commit shuffles around some of the `rand` code, along with some
reorganization. The new state of the world is as follows:
* The librand crate now only depends on libcore. This interface is experimental.
* The standard library has a new module, `std::rand`. This interface will
eventually become stable.
Unfortunately, this entailed more of a breaking change than just shuffling some
names around. The following breaking changes were made to the rand library:
* Rng::gen_vec() was removed. This has been replaced with Rng::gen_iter() which
will return an infinite stream of random values. Previous behavior can be
regained with `rng.gen_iter().take(n).collect()`
* Rng::gen_ascii_str() was removed. This has been replaced with
Rng::gen_ascii_chars() which will return an infinite stream of random ascii
characters. Similarly to gen_iter(), previous behavior can be emulated with
`rng.gen_ascii_chars().take(n).collect()`
* {IsaacRng, Isaac64Rng, XorShiftRng}::new() have all been removed. These all
relied on being able to use an OSRng for seeding, but this is no longer
available in librand (where these types are defined). To retain the same
functionality, these types now implement the `Rand` trait so they can be
generated with a random seed from another random number generator. This allows
the stdlib to use an OSRng to create seeded instances of these RNGs.
* Rand implementations for `Box<T>` and `@T` were removed. These seemed to be
pretty rare in the codebase, and it allows for librand to not depend on
liballoc. Additionally, other pointer types like Rc<T> and Arc<T> were not
supported. If this is undesirable, librand can depend on liballoc and regain
these implementations.
* The WeightedChoice structure is no longer built with a `Vec<Weighted<T>>`,
but rather a `&mut [Weighted<T>]`. This means that the WeightedChoice
structure now has a lifetime associated with it.
* The `sample` method on `Rng` has been moved to a top-level function in the
`rand` module due to its dependence on `Vec`.
cc #13851
[breaking-change]
2014-05-25 10:39:37 +02:00
|
|
|
DEPS_num := std
|
2015-01-20 19:45:29 +01:00
|
|
|
DEPS_test := std getopts serialize rbml term native:rust_test_helpers
|
std: Recreate a `rand` module
This commit shuffles around some of the `rand` code, along with some
reorganization. The new state of the world is as follows:
* The librand crate now only depends on libcore. This interface is experimental.
* The standard library has a new module, `std::rand`. This interface will
eventually become stable.
Unfortunately, this entailed more of a breaking change than just shuffling some
names around. The following breaking changes were made to the rand library:
* Rng::gen_vec() was removed. This has been replaced with Rng::gen_iter() which
will return an infinite stream of random values. Previous behavior can be
regained with `rng.gen_iter().take(n).collect()`
* Rng::gen_ascii_str() was removed. This has been replaced with
Rng::gen_ascii_chars() which will return an infinite stream of random ascii
characters. Similarly to gen_iter(), previous behavior can be emulated with
`rng.gen_ascii_chars().take(n).collect()`
* {IsaacRng, Isaac64Rng, XorShiftRng}::new() have all been removed. These all
relied on being able to use an OSRng for seeding, but this is no longer
available in librand (where these types are defined). To retain the same
functionality, these types now implement the `Rand` trait so they can be
generated with a random seed from another random number generator. This allows
the stdlib to use an OSRng to create seeded instances of these RNGs.
* Rand implementations for `Box<T>` and `@T` were removed. These seemed to be
pretty rare in the codebase, and it allows for librand to not depend on
liballoc. Additionally, other pointer types like Rc<T> and Arc<T> were not
supported. If this is undesirable, librand can depend on liballoc and regain
these implementations.
* The WeightedChoice structure is no longer built with a `Vec<Weighted<T>>`,
but rather a `&mut [Weighted<T>]`. This means that the WeightedChoice
structure now has a lifetime associated with it.
* The `sample` method on `Rng` has been moved to a top-level function in the
`rand` module due to its dependence on `Vec`.
cc #13851
[breaking-change]
2014-05-25 10:39:37 +02:00
|
|
|
DEPS_rand := core
|
2015-01-20 19:45:29 +01:00
|
|
|
DEPS_log := std
|
2014-05-06 18:52:53 +02:00
|
|
|
DEPS_fmt_macros = std
|
2015-06-25 19:07:01 +02:00
|
|
|
DEPS_alloc_system := core libc
|
2014-01-25 04:27:22 +01:00
|
|
|
|
2014-11-14 22:55:57 +01:00
|
|
|
TOOL_DEPS_compiletest := test getopts
|
|
|
|
TOOL_DEPS_rustdoc := rustdoc
|
2014-11-27 15:57:47 +01:00
|
|
|
TOOL_DEPS_rustc := rustc_driver
|
2015-01-20 19:45:29 +01:00
|
|
|
TOOL_DEPS_rustbook := std rustdoc
|
2015-05-03 02:57:41 +02:00
|
|
|
TOOL_DEPS_error-index-generator := rustdoc syntax serialize
|
2014-01-25 04:27:22 +01:00
|
|
|
TOOL_SOURCE_compiletest := $(S)src/compiletest/compiletest.rs
|
|
|
|
TOOL_SOURCE_rustdoc := $(S)src/driver/driver.rs
|
|
|
|
TOOL_SOURCE_rustc := $(S)src/driver/driver.rs
|
2014-12-02 15:20:48 +01:00
|
|
|
TOOL_SOURCE_rustbook := $(S)src/rustbook/main.rs
|
2015-05-03 02:57:41 +02:00
|
|
|
TOOL_SOURCE_error-index-generator := $(S)src/error-index-generator/main.rs
|
2014-01-25 04:27:22 +01:00
|
|
|
|
2014-05-01 05:05:14 +02:00
|
|
|
ONLY_RLIB_core := 1
|
2014-06-04 01:12:11 +02:00
|
|
|
ONLY_RLIB_libc := 1
|
2014-05-14 01:10:05 +02:00
|
|
|
ONLY_RLIB_alloc := 1
|
std: Recreate a `rand` module
This commit shuffles around some of the `rand` code, along with some
reorganization. The new state of the world is as follows:
* The librand crate now only depends on libcore. This interface is experimental.
* The standard library has a new module, `std::rand`. This interface will
eventually become stable.
Unfortunately, this entailed more of a breaking change than just shuffling some
names around. The following breaking changes were made to the rand library:
* Rng::gen_vec() was removed. This has been replaced with Rng::gen_iter() which
will return an infinite stream of random values. Previous behavior can be
regained with `rng.gen_iter().take(n).collect()`
* Rng::gen_ascii_str() was removed. This has been replaced with
Rng::gen_ascii_chars() which will return an infinite stream of random ascii
characters. Similarly to gen_iter(), previous behavior can be emulated with
`rng.gen_ascii_chars().take(n).collect()`
* {IsaacRng, Isaac64Rng, XorShiftRng}::new() have all been removed. These all
relied on being able to use an OSRng for seeding, but this is no longer
available in librand (where these types are defined). To retain the same
functionality, these types now implement the `Rand` trait so they can be
generated with a random seed from another random number generator. This allows
the stdlib to use an OSRng to create seeded instances of these RNGs.
* Rand implementations for `Box<T>` and `@T` were removed. These seemed to be
pretty rare in the codebase, and it allows for librand to not depend on
liballoc. Additionally, other pointer types like Rc<T> and Arc<T> were not
supported. If this is undesirable, librand can depend on liballoc and regain
these implementations.
* The WeightedChoice structure is no longer built with a `Vec<Weighted<T>>`,
but rather a `&mut [Weighted<T>]`. This means that the WeightedChoice
structure now has a lifetime associated with it.
* The `sample` method on `Rng` has been moved to a top-level function in the
`rand` module due to its dependence on `Vec`.
cc #13851
[breaking-change]
2014-05-25 10:39:37 +02:00
|
|
|
ONLY_RLIB_rand := 1
|
std: Recreate a `collections` module
As with the previous commit with `librand`, this commit shuffles around some
`collections` code. The new state of the world is similar to that of librand:
* The libcollections crate now only depends on libcore and liballoc.
* The standard library has a new module, `std::collections`. All functionality
of libcollections is reexported through this module.
I would like to stress that this change is purely cosmetic. There are very few
alterations to these primitives.
There are a number of notable points about the new organization:
* std::{str, slice, string, vec} all moved to libcollections. There is no reason
that these primitives shouldn't be necessarily usable in a freestanding
context that has allocation. These are all reexported in their usual places in
the standard library.
* The `hashmap`, and transitively the `lru_cache`, modules no longer reside in
`libcollections`, but rather in libstd. The reason for this is because the
`HashMap::new` contructor requires access to the OSRng for initially seeding
the hash map. Beyond this requirement, there is no reason that the hashmap
could not move to libcollections.
I do, however, have a plan to move the hash map to the collections module. The
`HashMap::new` function could be altered to require that the `H` hasher
parameter ascribe to the `Default` trait, allowing the entire `hashmap` module
to live in libcollections. The key idea would be that the default hasher would
be different in libstd. Something along the lines of:
// src/libstd/collections/mod.rs
pub type HashMap<K, V, H = RandomizedSipHasher> =
core_collections::HashMap<K, V, H>;
This is not possible today because you cannot invoke static methods through
type aliases. If we modified the compiler, however, to allow invocation of
static methods through type aliases, then this type definition would
essentially be switching the default hasher from `SipHasher` in libcollections
to a libstd-defined `RandomizedSipHasher` type. This type's `Default`
implementation would randomly seed the `SipHasher` instance, and otherwise
perform the same as `SipHasher`.
This future state doesn't seem incredibly far off, but until that time comes,
the hashmap module will live in libstd to not compromise on functionality.
* In preparation for the hashmap moving to libcollections, the `hash` module has
moved from libstd to libcollections. A previously snapshotted commit enables a
distinct `Writer` trait to live in the `hash` module which `Hash`
implementations are now parameterized over.
Due to using a custom trait, the `SipHasher` implementation has lost its
specialized methods for writing integers. These can be re-added
backwards-compatibly in the future via default methods if necessary, but the
FNV hashing should satisfy much of the need for speedier hashing.
A list of breaking changes:
* HashMap::{get, get_mut} no longer fails with the key formatted into the error
message with `{:?}`, instead, a generic message is printed. With backtraces,
it should still be not-too-hard to track down errors.
* The HashMap, HashSet, and LruCache types are now available through
std::collections instead of the collections crate.
* Manual implementations of hash should be parameterized over `hash::Writer`
instead of just `Writer`.
[breaking-change]
2014-05-30 03:50:12 +02:00
|
|
|
ONLY_RLIB_collections := 1
|
deprecate Unicode functions that will be moved to crates.io
This patch
1. renames libunicode to librustc_unicode,
2. deprecates several pieces of libunicode (see below), and
3. removes references to deprecated functions from
librustc_driver and libsyntax. This may change pretty-printed
output from these modules in cases involving wide or combining
characters used in filenames, identifiers, etc.
The following functions are marked deprecated:
1. char.width() and str.width():
--> use unicode-width crate
2. str.graphemes() and str.grapheme_indices():
--> use unicode-segmentation crate
3. str.nfd_chars(), str.nfkd_chars(), str.nfc_chars(), str.nfkc_chars(),
char.compose(), char.decompose_canonical(), char.decompose_compatible(),
char.canonical_combining_class():
--> use unicode-normalization crate
2015-04-14 21:52:37 +02:00
|
|
|
ONLY_RLIB_rustc_unicode := 1
|
2015-01-16 21:20:03 +01:00
|
|
|
ONLY_RLIB_rustc_bitflags := 1
|
2015-06-25 19:07:01 +02:00
|
|
|
ONLY_RLIB_alloc_system := 1
|
2014-05-01 05:05:14 +02:00
|
|
|
|
2015-04-08 00:11:16 +02:00
|
|
|
# Documented-by-default crates
|
deprecate Unicode functions that will be moved to crates.io
This patch
1. renames libunicode to librustc_unicode,
2. deprecates several pieces of libunicode (see below), and
3. removes references to deprecated functions from
librustc_driver and libsyntax. This may change pretty-printed
output from these modules in cases involving wide or combining
characters used in filenames, identifiers, etc.
The following functions are marked deprecated:
1. char.width() and str.width():
--> use unicode-width crate
2. str.graphemes() and str.grapheme_indices():
--> use unicode-segmentation crate
3. str.nfd_chars(), str.nfkd_chars(), str.nfc_chars(), str.nfkc_chars(),
char.compose(), char.decompose_canonical(), char.decompose_compatible(),
char.canonical_combining_class():
--> use unicode-normalization crate
2015-04-14 21:52:37 +02:00
|
|
|
DOC_CRATES := std alloc collections core libc rustc_unicode
|
2015-04-08 00:11:16 +02:00
|
|
|
|
2015-06-25 19:07:01 +02:00
|
|
|
ifeq ($(CFG_DISABLE_JEMALLOC),)
|
|
|
|
TARGET_CRATES += alloc_jemalloc
|
|
|
|
DEPS_std += alloc_jemalloc
|
|
|
|
DEPS_alloc_jemalloc := core libc native:jemalloc
|
|
|
|
ONLY_RLIB_alloc_jemalloc := 1
|
|
|
|
else
|
|
|
|
RUSTFLAGS_rustc_back := --cfg disable_jemalloc
|
|
|
|
endif
|
|
|
|
|
2014-01-25 04:27:22 +01:00
|
|
|
################################################################################
|
|
|
|
# You should not need to edit below this line
|
|
|
|
################################################################################
|
|
|
|
|
2015-06-25 19:07:01 +02:00
|
|
|
CRATES := $(TARGET_CRATES) $(HOST_CRATES)
|
|
|
|
|
2014-01-25 04:27:22 +01:00
|
|
|
# This macro creates some simple definitions for each crate being built, just
|
|
|
|
# some munging of all of the parameters above.
|
|
|
|
#
|
|
|
|
# $(1) is the crate to generate variables for
|
|
|
|
define RUST_CRATE
|
2015-06-12 19:40:07 +02:00
|
|
|
CRATEFILE_$(1) := $$(SREL)src/lib$(1)/lib.rs
|
2014-03-25 23:40:52 +01:00
|
|
|
RSINPUTS_$(1) := $$(call rwildcard,$(S)src/lib$(1)/,*.rs)
|
2014-01-25 04:27:22 +01:00
|
|
|
RUST_DEPS_$(1) := $$(filter-out native:%,$$(DEPS_$(1)))
|
|
|
|
NATIVE_DEPS_$(1) := $$(patsubst native:%,%,$$(filter native:%,$$(DEPS_$(1))))
|
|
|
|
endef
|
|
|
|
|
|
|
|
$(foreach crate,$(CRATES),$(eval $(call RUST_CRATE,$(crate))))
|
|
|
|
|
|
|
|
# Similar to the macro above for crates, this macro is for tools
|
|
|
|
#
|
|
|
|
# $(1) is the crate to generate variables for
|
|
|
|
define RUST_TOOL
|
2014-03-25 23:40:52 +01:00
|
|
|
TOOL_INPUTS_$(1) := $$(call rwildcard,$$(dir $$(TOOL_SOURCE_$(1))),*.rs)
|
2014-01-25 04:27:22 +01:00
|
|
|
endef
|
|
|
|
|
|
|
|
$(foreach crate,$(TOOLS),$(eval $(call RUST_TOOL,$(crate))))
|
2015-05-28 08:24:27 +02:00
|
|
|
|
|
|
|
ifdef CFG_DISABLE_ELF_TLS
|
|
|
|
RUSTFLAGS_std := --cfg no_elf_tls
|
|
|
|
endif
|