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

Age	Commit message (Collapse)	Author	Lines
2025-04-01	Allow formatting example/gen_block_iterate.rs	bjorn3	-4/+0

2025-02-15	Merge commit '557ed8ebb7e981817d03c87352892c394183dd70' into ↵	bjorn3	-1/+2
	sync_cg_clif-2025-02-15
2024-07-29	Update `use` declarations formatting options.	Nicholas Nethercote	-0/+2
	As decided in rust-lang/compiler-team#750. Use declarations are currently wildly inconsistent because rustfmt is quite unopinionated about how they should be formatted. The `rustfmt.toml` additions makes rustfmt more opinionated, which avoids the need for any decision when adding new use declarations to a file. This commit only updates `rustfmt.toml` and `compiler/rustc_codegen_cranelift/rustfmt.toml`. The next commit will do the reformatting.
2024-03-08	Merge commit '54cbb6e7531f95e086d5c3dd0d5e73bfbe3545ba' into ↵	bjorn3	-1/+0
	sync_cg_clif-2024-03-08
2023-11-23	Fix fn_sig_for_fn_abi and the coroutine transform for generators	bjorn3	-1/+4
	There were three issues previously: * The self argument was pinned, despite Iterator::next taking an unpinned mutable reference. * A resume argument was passed, despite Iterator::next not having one. * The return value was CoroutineState<Item, ()> rather than Option<Item> While these things just so happened to work with the LLVM backend, cg_clif does much stricter checks when trying to assign a value to a place. In addition it can't handle the mismatch between the amount of arguments specified by the FnAbi and the FnSig.
2022-12-14	Merge commit '2bb3996244cf1b89878da9e39841e9f6bf061602' into ↵	bjorn3	-0/+2
	sync_cg_clif-2022-12-14
2021-03-05	Merge commit '9a0c32934ebe376128230aa8da3275697b2053e7' into ↵	bjorn3	-0/+4
	sync_cg_clif-2021-03-05