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

Age	Commit message (Collapse)	Author	Lines
2020-11-13	Auto merge of #78826 - petrochenkov:mrscopes2, r=eddyb	bors	-14/+23
	resolve: Collapse `macro_rules` scope chains on the fly Otherwise they grow too long and you have to endlessly walk through them when resolving macros or imports. Addresses https://rust-lang.zulipchat.com/#narrow/stream/247081-t-compiler.2Fperformance/topic/Slow.20Builtin.20Derives/near/215750815
2020-11-08	rustc_resolve: Use `#![feature(format_args_capture)]`	Vadim Petrochenkov	-0/+1

2020-11-07	resolve: Collapse `macro_rules` scope chains on the fly	Vadim Petrochenkov	-14/+23

2020-10-30	Fix even more clippy warnings	Joshua Nelson	-50/+30

2020-10-28	[resolve] Use `unwrap_or_else` instead of `unwrap_or` in a hot path	Wesley Wiser	-4/+3
	This improves the performance of the `resolve_crate` function by 30% for a very large single file crate with auto-generated C bindings.
2020-10-22	Auto merge of #78134 - bugadani:arena-nodrop, r=lcnr	bors	-7/+5
	Use `DroplessArena` where we know the type doesn't need drop This PR uses a single `DroplessArena` in resolve instead of three separate `TypedArena`s. `DroplessArena` checks that the type indeed doesn't need drop, so in case the types change, this will result in visible failures.
2020-10-20	Resolve: Use dropless arena for types that don't need drop	Dániel Buga	-7/+5

2020-10-19	Calculate visibilities once in resolve	Vadim Petrochenkov	-9/+16
	Then use them through a query based on resolver outputs
2020-10-17	resolve: Do not put nonexistent crate `meta` into prelude	Vadim Petrochenkov	-3/+0

2020-10-11	`min_const_generics` diagnostics improvements	Ethan Brierley	-1/+1
	2 3
2020-10-03	Replace "non trivial" with "non-trivial"	varkor	-1/+1

2020-09-23	/nightly/nightly-rustc	Erik Hofmayer	-1/+1

2020-09-23	Updated html_root_url for compiler crates	Erik Hofmayer	-1/+1

2020-09-20	use if let instead of single match arm expressions to compact code and ↵	Matthias Krüger	-5/+2
	reduce nesting (clippy::single_match)
2020-09-15	This commit introduces the following changes:	Hameer Abbasi	-5/+9
	* Change error message for type param in a const expression when using min_const_generics * Change ParamInNonTrivialAnonConst to contain an extra bool used for distinguishing whether the passed-in symbol is a type or a value.
2020-09-13	review, improve note span	Bastian Kauschke	-18/+16

2020-09-13	allow concrete self types in consts	Bastian Kauschke	-9/+20

2020-09-11	Auto merge of #76499 - guswynn:priv_des, r=petrochenkov	bors	-1/+6
	Give better diagnostic when using a private tuple struct constructor Fixes #75907 Some notes: 1. This required some deep changes, including removing a Copy impl for PatKind. If some tests fail, I would still appreciate review on the overall approach 2. this only works with basic patterns (no wildcards for example), and fails if there is any problems getting the visibility of the fields (i am not sure what the failure that can happen in resolve_visibility_speculative, but we check the length of our fields in both cases against each other, so if anything goes wrong, we fall back to the worse error. This could be extended to more patterns 3. this does not yet deal with #75906, but I believe it will be similar 4. let me know if you want more tests 5. doesn't yet at the suggestion that `@yoshuawuyts` suggested at the end of their issue, but that could be added relatively easily (i believe)
2020-09-11	Give better diagnostic when using a private tuple struct constructor	Gus Wynn	-1/+6

2020-09-10	Attach `TokenStream` to `ast::Path`	Aaron Hill	-0/+2

2020-09-09	Rollup merge of #75984 - kornelski:typeormodule, r=matthewjasper	Tyler Mandry	-1/+8
	Improve unresolved use error message "use of undeclared type or module `foo`" doesn't mention that it could be a crate. This error can happen when users forget to add a dependency to `Cargo.toml`, so I think it's important to mention that it could be a missing crate. I've used a heuristic based on Rust's naming conventions. It complains about an unknown type if the ident starts with an upper-case letter, and crate or module otherwise. It seems to work very well. The expanded error help covers both an unknown type and a missing crate case.
2020-09-01	Clarify message about unresolved use	Kornel	-1/+8

2020-09-01	Give a better error message for duplicate built-in macros	Joshua Nelson	-1/+7
	Previously, this would say no such macro existed, but this was misleading, since the macro _did_ exist, it was just already seen. - Say where the macro was previously defined - Add long-form error message
2020-08-30	mv compiler to compiler/	mark	-0/+3328