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

Age	Commit message (Collapse)	Author	Lines
2020-12-19	Revert "Promote missing_fragment_specifier to hard error"	Wesley Wiser	-1/+18
	This reverts commit 02eae432e7476a0686633a8c2b7cb1d5aab1bd2c.
2020-11-02	Rollup merge of #78610 - petrochenkov:nostriptok, r=Aaron1011	Yuki Okushi	-88/+2
	Do not remove tokens before AST json serialization `TokenStripper` is error-prone and introduces one more use of `MutVisitor`. It's much simpler to treat serialization as just one more place that wants lazy token stream to turn into a real token stream. Also, no code is better than more code, in general. r? @Aaron1011 (I also merged tests for `TokenStripper` ICEs into one.)
2020-11-01	Auto merge of #75534 - Aaron1011:feature/new-future-breakage, r=pnkfelix	bors	-1/+4
	Implement rustc side of report-future-incompat cc https://github.com/rust-lang/rust/issues/71249 This is an alternative to `@pnkfelix's` initial implementation in https://github.com/pnkfelix/rust/commits/prototype-rustc-side-of-report-future-incompat (mainly because I started working before seeing that branch :smile: ). My approach outputs the entire original `Diagnostic`, in a way that is compatible with incremental compilation. This is not yet integrated with compiletest, but can be used manually by passing `-Z emit-future-incompat-report` to `rustc`. Several changes are made to support this feature: * The `librustc_session/lint` module is moved to a new crate `librustc_lint_defs` (name bikesheddable). This allows accessing lint definitions from `librustc_errors`. * The `Lint` struct is extended with an `Option<FutureBreakage>`. When present, it indicates that we should display a lint in the future-compat report. `FutureBreakage` contains additional information that we may want to display in the report (currently, a `date` field indicating when the crate will stop compiling). * A new variant `rustc_error::Level::Allow` is added. This is used when constructing a diagnostic for a future-breakage lint that is marked as allowed (via `#[allow]` or `--cap-lints`). This allows us to capture any future-breakage diagnostics in one place, while still discarding them before they are passed to the `Emitter`. * `DiagnosticId::Lint` is extended with a `has_future_breakage` field, indicating whether or not the `Lint` has future breakage information (and should therefore show up in the report). * `Session` is given access to the `LintStore` via a new `SessionLintStore` trait (since `librustc_session` cannot directly reference `LintStore` without a cyclic dependency). We use this to turn a string `DiagnosticId::Lint` back into a `Lint`, to retrieve the `FutureBreakage` data. Currently, `FutureBreakage.date` is always set to `None`. However, this could potentially be interpreted by Cargo in the future. I've enabled the future-breakage report for the `ARRAY_INTO_ITER` lint, which can be used to test out this PR. The intent is to use the field to allow Cargo to determine the date of future breakage (as described in [RFC 2834](https://github.com/rust-lang/rfcs/blob/master/text/2834-cargo-report-future-incompat.md)) without needing to parse the diagnostic itself. cc `@pnkfelix`
2020-11-01	Do not remove tokens before AST json serialization	Vadim Petrochenkov	-88/+2

2020-10-30	Implement rustc side of report-future-incompat	Aaron Hill	-1/+4

2020-10-29	Strip tokens from trait and impl items before printing AST JSON	Aaron Hill	-0/+11
	Fixes #78510
2020-10-26	Remove tokens from foreign items in `TokenStripper`	Aaron Hill	-0/+7
	Fixes #78398 I forgot to handle this case in #77255
2020-10-21	Strip tokens before printing AST JSON	Aaron Hill	-2/+70

2020-10-05	Add -Z codegen-backend dylib to deps	khyperia	-0/+4
	When the codegen-backend dylib changes, the program should be rebuilt.
2020-09-01	interface: use `OnceCell` from standard library	marmeladema	-3/+3

2020-08-30	Add `-Z proc-macro-backtrace` to allow showing proc-macro panics	Aaron Hill	-0/+1
	Fixes #75050 Previously, we would unconditionally suppress the panic hook during proc-macro execution. This commit adds a new flag -Z proc-macro-backtrace, which allows running the panic hook for easier debugging.
2020-08-30	mv compiler to compiler/	mark	-0/+1004