rust/compiler/rustc_ast/Cargo.toml

[package]
name = "rustc_ast"
version = "0.0.0"
edition = "2021"

[dependencies]
# FIXME: bumping memchr to 2.7.1 causes linker errors in MSVC thin-lto
# tidy-alphabetical-start
bitflags = "2.4.1"
memchr = "=2.5.0"
rustc_ast_ir = { path = "../rustc_ast_ir" }
rustc_data_structures = { path = "../rustc_data_structures" }
rustc_index = { path = "../rustc_index" }
rustc_lexer = { path = "../rustc_lexer" }
rustc_macros = { path = "../rustc_macros" }
rustc_serialize = { path = "../rustc_serialize" }
rustc_span = { path = "../rustc_span" }
smallvec = { version = "1.8.1", features = ["union", "may_dangle"] }
thin-vec = "0.2.12"
tracing = "0.1"
# tidy-alphabetical-end
mv compiler to compiler/ 2020-08-28 03:58:48 +00:00			`[package]`
			`name = "rustc_ast"`
			`version = "0.0.0"`
Migrate to 2021 2021-09-19 16:49:55 +00:00			`edition = "2021"`
mv compiler to compiler/ 2020-08-28 03:58:48 +00:00
			`[dependencies]`
Pin `memchr` version 2024-02-06 22:26:16 +00:00			`# FIXME: bumping memchr to 2.7.1 causes linker errors in MSVC thin-lto`
Clean up `rustc_*/Cargo.toml`. - Sort dependencies and features sections. - Add `tidy` markers to the sorted sections so they stay sorted. - Remove empty `[lib`] sections. - Remove "See more keys..." comments. Excluded files: - rustc_codegen_{cranelift,gcc}, because they're external. - rustc_lexer, because it has external use. - stable_mir, because it has external use. 2023-10-20 02:37:29 +00:00			`# tidy-alphabetical-start`
Update to bitflags 2 in the compiler This involves lots of breaking changes. There are two big changes that force changes. The first is that the bitflag types now don't automatically implement normal derive traits, so we need to derive them manually. Additionally, bitflags now have a hidden inner type by default, which breaks our custom derives. The bitflags docs recommend using the impl form in these cases, which I did. 2023-12-30 16:09:02 +00:00			`bitflags = "2.4.1"`
Pin `memchr` version 2024-02-06 22:26:16 +00:00			`memchr = "=2.5.0"`
Split rustc_type_ir to avoid rustc_ast from depending on it 2024-02-27 18:11:23 +00:00			`rustc_ast_ir = { path = "../rustc_ast_ir" }`
mv compiler to compiler/ 2020-08-28 03:58:48 +00:00			`rustc_data_structures = { path = "../rustc_data_structures" }`
			`rustc_index = { path = "../rustc_index" }`
			`rustc_lexer = { path = "../rustc_lexer" }`
			`rustc_macros = { path = "../rustc_macros" }`
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-17 04:22:30 +00:00			`rustc_serialize = { path = "../rustc_serialize" }`
			`rustc_span = { path = "../rustc_span" }`
Update `smallvec` to 1.8.1. This pulls in https://github.com/servo/rust-smallvec/pull/282, which gives some small wins for rustc. 2022-06-26 22:48:55 +00:00			`smallvec = { version = "1.8.1", features = ["union", "may_dangle"] }`
Upgrade `thin-vec` from 0.2.9 to 0.2.12. Because 0.2.10 added supports for `ThinVec::splice`, and 0.2.12 is the latest release. 2022-12-05 23:19:32 +00:00			`thin-vec = "0.2.12"`
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-17 04:22:30 +00:00			`tracing = "0.1"`
Clean up `rustc_*/Cargo.toml`. - Sort dependencies and features sections. - Add `tidy` markers to the sorted sections so they stay sorted. - Remove empty `[lib`] sections. - Remove "See more keys..." comments. Excluded files: - rustc_codegen_{cranelift,gcc}, because they're external. - rustc_lexer, because it has external use. - stable_mir, because it has external use. 2023-10-20 02:37:29 +00:00			`# tidy-alphabetical-end`