mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
51b03639d6
rust/compiler/rustc_middle/Cargo.toml

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

40 lines
1.2 KiB
TOML
Raw Normal View History

mv compiler to compiler/
2020-08-27 22:58:48 -05:00
[package]
name = "rustc_middle"
version = "0.0.0"
Migrate to 2021
2021-09-19 11:49:55 -05:00
edition = "2021"
mv compiler to compiler/
2020-08-27 22:58:48 -05:00
[lib]
doctest = false
[dependencies]
bitflags = "1.2.1"
Replace `rustc_data_structures::thin_vec::ThinVec` with `thin_vec::ThinVec`. `rustc_data_structures::thin_vec::ThinVec` looks like this: ``` pub struct ThinVec<T>(Option<Box<Vec<T>>>); ``` It's just a zero word if the vector is empty, but requires two allocations if it is non-empty. So it's only usable in cases where the vector is empty most of the time. This commit removes it in favour of `thin_vec::ThinVec`, which is also word-sized, but stores the length and capacity in the same allocation as the elements. It's good in a wider variety of situation, e.g. in enum variants where the vector is usually/always non-empty. The commit also: - Sorts some `Cargo.toml` dependency lists, to make additions easier. - Sorts some `use` item lists, to make additions easier. - Changes `clean_trait_ref_with_bindings` to take a `ThinVec<TypeBinding>` rather than a `&[TypeBinding]`, because this avoid some unnecessary allocations.
2022-08-16 23:22:30 -05:00
chalk-ir = "0.80.0"
Move the dataflow framework to its own crate.
2021-01-05 12:53:07 -06:00
either = "1.5.0"
revert #92254 "Bump gsgdt to 0.1.3" gsgdt 0.1.3 was yanked: https://github.com/rust-lang/rust/pull/92254#issuecomment-1004269481
2022-01-03 13:25:46 -06:00
gsgdt = "0.1.2"
update polonius-engine to 0.13 and update fact generation to the new relation names
2021-07-22 15:21:06 -05:00
polonius-engine = "0.13.0"
mv compiler to compiler/
2020-08-27 22:58:48 -05:00
rustc_apfloat = { path = "../rustc_apfloat" }
Replace `rustc_data_structures::thin_vec::ThinVec` with `thin_vec::ThinVec`. `rustc_data_structures::thin_vec::ThinVec` looks like this: ``` pub struct ThinVec<T>(Option<Box<Vec<T>>>); ``` It's just a zero word if the vector is empty, but requires two allocations if it is non-empty. So it's only usable in cases where the vector is empty most of the time. This commit removes it in favour of `thin_vec::ThinVec`, which is also word-sized, but stores the length and capacity in the same allocation as the elements. It's good in a wider variety of situation, e.g. in enum variants where the vector is usually/always non-empty. The commit also: - Sorts some `Cargo.toml` dependency lists, to make additions easier. - Sorts some `use` item lists, to make additions easier. - Changes `clean_trait_ref_with_bindings` to take a `ThinVec<TypeBinding>` rather than a `&[TypeBinding]`, because this avoid some unnecessary allocations.
2022-08-16 23:22:30 -05:00
rustc_arena = { path = "../rustc_arena" }
rustc_ast = { path = "../rustc_ast" }
mv compiler to compiler/
2020-08-27 22:58:48 -05:00
rustc_attr = { path = "../rustc_attr" }
rustc_data_structures = { path = "../rustc_data_structures" }
rustc_errors = { path = "../rustc_errors" }
Replace `rustc_data_structures::thin_vec::ThinVec` with `thin_vec::ThinVec`. `rustc_data_structures::thin_vec::ThinVec` looks like this: ``` pub struct ThinVec<T>(Option<Box<Vec<T>>>); ``` It's just a zero word if the vector is empty, but requires two allocations if it is non-empty. So it's only usable in cases where the vector is empty most of the time. This commit removes it in favour of `thin_vec::ThinVec`, which is also word-sized, but stores the length and capacity in the same allocation as the elements. It's good in a wider variety of situation, e.g. in enum variants where the vector is usually/always non-empty. The commit also: - Sorts some `Cargo.toml` dependency lists, to make additions easier. - Sorts some `use` item lists, to make additions easier. - Changes `clean_trait_ref_with_bindings` to take a `ThinVec<TypeBinding>` rather than a `&[TypeBinding]`, because this avoid some unnecessary allocations.
2022-08-16 23:22:30 -05:00
rustc_feature = { path = "../rustc_feature" }
Move the dataflow framework to its own crate.
2021-01-05 12:53:07 -06:00
rustc_graphviz = { path = "../rustc_graphviz" }
Replace `rustc_data_structures::thin_vec::ThinVec` with `thin_vec::ThinVec`. `rustc_data_structures::thin_vec::ThinVec` looks like this: ``` pub struct ThinVec<T>(Option<Box<Vec<T>>>); ``` It's just a zero word if the vector is empty, but requires two allocations if it is non-empty. So it's only usable in cases where the vector is empty most of the time. This commit removes it in favour of `thin_vec::ThinVec`, which is also word-sized, but stores the length and capacity in the same allocation as the elements. It's good in a wider variety of situation, e.g. in enum variants where the vector is usually/always non-empty. The commit also: - Sorts some `Cargo.toml` dependency lists, to make additions easier. - Sorts some `use` item lists, to make additions easier. - Changes `clean_trait_ref_with_bindings` to take a `ThinVec<TypeBinding>` rather than a `&[TypeBinding]`, because this avoid some unnecessary allocations.
2022-08-16 23:22:30 -05:00
rustc_hir = { path = "../rustc_hir" }
mv compiler to compiler/
2020-08-27 22:58:48 -05:00
rustc_index = { path = "../rustc_index" }
Replace `rustc_data_structures::thin_vec::ThinVec` with `thin_vec::ThinVec`. `rustc_data_structures::thin_vec::ThinVec` looks like this: ``` pub struct ThinVec<T>(Option<Box<Vec<T>>>); ``` It's just a zero word if the vector is empty, but requires two allocations if it is non-empty. So it's only usable in cases where the vector is empty most of the time. This commit removes it in favour of `thin_vec::ThinVec`, which is also word-sized, but stores the length and capacity in the same allocation as the elements. It's good in a wider variety of situation, e.g. in enum variants where the vector is usually/always non-empty. The commit also: - Sorts some `Cargo.toml` dependency lists, to make additions easier. - Sorts some `use` item lists, to make additions easier. - Changes `clean_trait_ref_with_bindings` to take a `ThinVec<TypeBinding>` rather than a `&[TypeBinding]`, because this avoid some unnecessary allocations.
2022-08-16 23:22:30 -05:00
rustc_macros = { path = "../rustc_macros" }
rustc_query_system = { path = "../rustc_query_system" }
rustc-rayon-core = { version = "0.4.0", optional = true }
rustc-rayon = { version = "0.4.0", optional = true }
mv compiler to compiler/
2020-08-27 22:58:48 -05:00
rustc_serialize = { path = "../rustc_serialize" }
rustc_session = { path = "../rustc_session" }
Replace `rustc_data_structures::thin_vec::ThinVec` with `thin_vec::ThinVec`. `rustc_data_structures::thin_vec::ThinVec` looks like this: ``` pub struct ThinVec<T>(Option<Box<Vec<T>>>); ``` It's just a zero word if the vector is empty, but requires two allocations if it is non-empty. So it's only usable in cases where the vector is empty most of the time. This commit removes it in favour of `thin_vec::ThinVec`, which is also word-sized, but stores the length and capacity in the same allocation as the elements. It's good in a wider variety of situation, e.g. in enum variants where the vector is usually/always non-empty. The commit also: - Sorts some `Cargo.toml` dependency lists, to make additions easier. - Sorts some `use` item lists, to make additions easier. - Changes `clean_trait_ref_with_bindings` to take a `ThinVec<TypeBinding>` rather than a `&[TypeBinding]`, because this avoid some unnecessary allocations.
2022-08-16 23:22:30 -05:00
rustc_span = { path = "../rustc_span" }
rustc_target = { path = "../rustc_target" }
Create `rustc_ty_library`
2020-11-18 09:37:10 -06:00
rustc_type_ir = { path = "../rustc_type_ir" }
Replace `rustc_data_structures::thin_vec::ThinVec` with `thin_vec::ThinVec`. `rustc_data_structures::thin_vec::ThinVec` looks like this: ``` pub struct ThinVec<T>(Option<Box<Vec<T>>>); ``` It's just a zero word if the vector is empty, but requires two allocations if it is non-empty. So it's only usable in cases where the vector is empty most of the time. This commit removes it in favour of `thin_vec::ThinVec`, which is also word-sized, but stores the length and capacity in the same allocation as the elements. It's good in a wider variety of situation, e.g. in enum variants where the vector is usually/always non-empty. The commit also: - Sorts some `Cargo.toml` dependency lists, to make additions easier. - Sorts some `use` item lists, to make additions easier. - Changes `clean_trait_ref_with_bindings` to take a `ThinVec<TypeBinding>` rather than a `&[TypeBinding]`, because this avoid some unnecessary allocations.
2022-08-16 23:22:30 -05:00
smallvec = { version = "1.8.1", features = ["union", "may_dangle"] }
thin-vec = "0.2.8"
tracing = "0.1"
Propagate `parallel_compiler` feature through rustc crates. Turned off feature gives change of builded crates: 238 -> 224.
2022-02-11 14:25:14 -06:00
[features]
rustc_use_parallel_compiler = ["rustc-rayon", "rustc-rayon-core"]
Reference in New Issue Copy Permalink