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

Age	Commit message (Collapse)	Author	Lines
2021-02-18	Add explanations and suggestions to `irrefutable_let_patterns` lint	Camelid	-0/+16

2021-02-18	Rollup merge of #82215 - TaKO8Ki:replace-if-let-while-let, r=varkor	Dylan DPC	-16/+16
	Replace if-let and while-let with `if let` and `while let` This pull request replaces if-let and while-let with `if let` and `while let`. closes https://github.com/rust-lang/rust/issues/82205
2021-02-17	replace if-let and while-let with `if let` and `while let`	Takayuki Maeda	-16/+16

2021-02-16	Move some tests to more reasonable directories	Caio	-0/+45

2020-12-04	Move format machinery tests to where they belong	Aleksey Kladov	-486/+0

2020-11-24	Move src/test/ui/if-.rs to src/test/expr/if/if-.rs	Havvy (Ryan Scheel)	-0/+195

2020-11-24	Move src/test/ui/if-attrs to src/test/ui/expr/if/attrs	Havvy (Ryan Scheel)	-0/+176

2020-11-24	Move src/test/ui/if to src/test/ui/expr/if	Havvy (Ryan Scheel)	-0/+1025

2020-11-22	Add test for eval order for a+=b	Havvy (Ryan Scheel)	-0/+76
	Yes, the order of evaluation does change depending on the types of the operands. Cursed, I know. I've elected to place this test into `expr/compound-assignment` creating both the `expr` directory and the `compound-assignment` directory. I plan in a future PR to also move the `if` directory and the loose `if` tests into `expr/if` and other similar cleanups of the `test/ui` directory. Future work: Test more than just `+=`, but all operators. I don't know if using a macro to generate these tests cases would be okay or not, but it'd be boilerplatey without it. I'm also confident you cannot change the evaluation order of one operator without changing all of them. Future work: Additionally, test more than just `i32 += i32` for the primitive version. I don't actually know the full set of primitive implementations, but I imagine there's enough to cause a combinatorial explosion with the previous future work item. Somewhere on the order of one to two hundred individual functions.