rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2025-01-20	proc_macro: add `#![warn(unreachable_pub)]`	Urgau	-2/+2

2024-12-23	Use `#[derive(Default)]` instead of manually implementing it	Esteban Küber	-7/+1

2024-07-29	Reformat `use` declarations.	Nicholas Nethercote	-2/+1
	The previous commit updated `rustfmt.toml` appropriately. This commit is the outcome of running `x fmt --all` with the new formatting options.
2024-06-05	Rollup merge of #123168 - joshtriplett:size-of-prelude, r=Amanieu	Jubilee	-1/+0
	Add `size_of` and `size_of_val` and `align_of` and `align_of_val` to the prelude (Note: need to update the PR to add `align_of` and `align_of_val`, and remove the second commit with the myriad changes to appease the lint.) Many, many projects use `size_of` to get the size of a type. However, it's also often equally easy to hardcode a size (e.g. `8` instead of `size_of::<u64>()`). Minimizing friction in the use of `size_of` helps ensure that people use it and make code more self-documenting. The name `size_of` is unambiguous: the name alone, without any prefix or path, is self-explanatory and unmistakeable for any other functionality. Adding it to the prelude cannot produce any name conflicts, as any local definition will silently shadow the one from the prelude. Thus, we don't need to wait for a new edition prelude to add it.
2024-05-30	Apply x clippy --fix and x fmt	r0cky	-1/+1

2024-05-13	Add `size_of`, `size_of_val`, `align_of`, and `align_of_val` to the prelude	Josh Triplett	-1/+0
	Many, many projects use `size_of` to get the size of a type. However, it's also often equally easy to hardcode a size (e.g. `8` instead of `size_of::<u64>()`). Minimizing friction in the use of `size_of` helps ensure that people use it and make code more self-documenting. The name `size_of` is unambiguous: the name alone, without any prefix or path, is self-explanatory and unmistakeable for any other functionality. Adding it to the prelude cannot produce any name conflicts, as any local definition will silently shadow the one from the prelude. Thus, we don't need to wait for a new edition prelude to add it. Add `size_of_val`, `align_of`, and `align_of_val` as well, with similar justification: widely useful, self-explanatory, unmistakeable for anything else, won't produce conflicts.
2023-04-12	remove some unneeded imports	KaDiWa	-2/+0

2022-12-30	Replace libstd, libcore, liballoc in docs.	jonathanCogan	-3/+3

2022-07-18	proc_macro: use fxhash within the proc_macro crate	Nika Layzell	-0/+117
	Unfortunately, as it is difficult to depend on crates from within proc_macro, this is done by vendoring a copy of the hasher as a module rather than depending on the rustc_hash crate. This probably doesn't have a substantial impact up-front, however will be more relevant once symbols are interned within the proc_macro client.