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

Age	Commit message (Collapse)	Author	Lines
2016-05-09	Auto merge of #33484 - murarth:diagnostic-builder-fields, r=brson	bors	-0/+8
	Add accessor methods to DiagnosticBuilder
2016-05-08	Rollup merge of #33369 - nikomatsakis:graceful-empty-span, r=jntrnr	Manish Goregaokar	-1/+49
	degrade gracefully with empty spans In https://github.com/rust-lang/rust/pull/32756, we solved the final test failure, but digging more into it the handling of that scenario could be better. The error was caused by an empty span supplied by the parser representing EOF. This patch checks that we cope more gracefully with such spans: r? @jonathandturner
2016-05-07	Add accessor methods to DiagnosticBuilder	Murarth	-0/+8

2016-05-03	Remove unused trait imports introduced while in review	Seo Sanghyeon	-1/+1

2016-05-03	degrade gracefully with empty spans	Niko Matsakis	-1/+49

2016-05-02	assert we get at least two rendered lines back	Niko Matsakis	-2/+5

2016-05-02	avoid double panic	Niko Matsakis	-1/+2

2016-05-02	do not fail if len(rendered_lines) is == 1	Niko Matsakis	-10/+14
	also handle more rendered-lines
2016-05-02	update unit tests	Niko Matsakis	-39/+38

2016-05-02	Finish up with 'old school' error mode	Jonathan Turner	-12/+63

2016-05-02	Add back in a 'old school' error format	Jonathan Turner	-50/+201

2016-05-02	change color of warning to YELLOW	Niko Matsakis	-1/+1

2016-05-02	fix snippet tests MORE!	Niko Matsakis	-2/+2

2016-05-02	Nit: use Range::contains	Niko Matsakis	-7/+2

2016-05-02	fix tests better	Niko Matsakis	-5/+5

2016-05-02	only emit `^` at the start of a multi-line error	Niko Matsakis	-143/+67
	as a result, simplify elision code
2016-05-02	Nit: use last_mut better	Niko Matsakis	-4/+3

2016-05-02	Nit: in emitter.rs	Niko Matsakis	-2/+1

2016-05-02	Nit: address various style nits	Niko Matsakis	-5/+10

2016-05-02	Nit: do not use RLK	Niko Matsakis	-12/+14

2016-05-02	Nit: do not import variants from Style	Niko Matsakis	-24/+23

2016-05-02	Do not import variants from RenderedLineKind	Niko Matsakis	-12/+12

2016-05-02	refactor the Emitter trait	Niko Matsakis	-98/+74
	There is now a CoreEmitter that everything desugars to, but without losing any information. Also remove RenderSpan::FileLine. This lets the rustc_driver tests build.
2016-05-02	change errors from Yellow to Magenta	Niko Matsakis	-1/+1
	The Yellow text is very hard to read with a white background.
2016-05-02	WIP factor out RudimentaryEmitter	Niko Matsakis	-16/+31

2016-05-02	refactor to use new snippet code and model	Niko Matsakis	-649/+322
	Major changes: - Remove old snippet rendering code and use the new stuff. - Introduce `span_label` method to add a label - Remove EndSpan mode and replace with a fn to get the last character of a span. - Stop using `Option<MultiSpan>` and just use an empty `MultiSpan` - and probably a bunch of other stuff :)
2016-05-02	adapt JSON to new model	Niko Matsakis	-119/+83
	Each Span now carries a `is_primary` boolean along with an optional label. If there are multiple labels for a span, it will appear multiple times.
2016-05-02	revamp MultiSpan and introduce new snippet code	Niko Matsakis	-0/+1345
	MultiSpan model is now: - set of primary spans - set of span+label pairs Primary spans render with `^^^`, secondary spans with `---`. Labels are placed next to the `^^^` or `---` marker as appropriate.
2016-04-27	Make some fatal lexer errors recoverable	mitaa	-0/+2

2016-04-21	pacify the merciless acrichto (somewhat)	Niko Matsakis	-8/+6
	Also add a comment or two to pacify the merciless self-critic, who hates a closure without a comment.
2016-04-21	port compiletest to use JSON output	Niko Matsakis	-122/+176
	This uncovered a lot of bugs in compiletest and also some shortcomings of our existing JSON output. We had to add information to the JSON output, such as suggested text and macro backtraces. We also had to fix various bugs in the existing tests. Joint work with jntrnr.
2016-04-12	Remove unused trait imports	Seo Sanghyeon	-3/+0

2016-04-04	Give better spans for SpanEnd errors	Nick Cameron	-15/+60

2016-03-30	Put in `-Z continue-parse-after-error`	Felix S. Klock II	-0/+9
	This works by adding a boolean flag, `continue_after_error`, to `syntax::errors::Handler` that can be imperatively set to `true` or `false` via a new `fn set_continue_after_error`. The flag starts off true (since we generally try to recover from compiler errors, and `Handler` is shared across all phases). Then, during the `phase_1_parse_input`, we consult the setting of the `-Z continue-parse-after-error` debug flag to determine whether we should leave the flag set to `true` or should change it to `false`. ---- (We might consider adding a debugflag to do such aborts in other places where we are currently attempting recovery, such as resolve, but I think the parser is the really important case to handle in the face of #31994 and the parser bugs of varying degrees that were injected by parse error recovery.)
2016-03-24	Include source text in JSON errors	Nick Cameron	-1/+39

2016-03-22	fix alignment	Jorge Aparicio	-12/+12

2016-03-22	try! -> ?	Jorge Aparicio	-38/+38
	Automated conversion using the untry tool [1] and the following command: ``` $ find -name '*.rs' -type f \| xargs untry ``` at the root of the Rust repo. [1]: https://github.com/japaric/untry
2016-02-03	Fix rendering of single-char-span	mitaa	-10/+10
	A span spanning only a single character would render like `^~` instead of just `^`.
2016-02-02	Rollup merge of #31281 - oli-obk:patch-2, r=nikomatsakis	Steve Klabnik	-2/+2

2016-02-01	Spans now derive equality	Daniel Campbell	-5/+3

2016-01-30	off by one	Oliver Schneider	-1/+1

2016-01-29	Update emitter.rs	mitaa	-1/+1

2016-01-29	fix overflow due to multiline error span	Oliver Schneider	-1/+1

2016-01-28	Implement MultiSpan error reporting	mitaa	-377/+873
	This allows to render multiple spans on one line, or to splice multiple replacements into a code suggestion.
2016-01-26	Rollup merge of #31211 - Manishearth:pr-30765, r=nrc	Manish Goregaokar	-2/+2
	r? @eddyb or @nrc
2016-01-26	Make emitter handle DUMMY_SP correctly	Manish Goregaokar	-2/+2

2016-01-22	The war on abort_if_errors	Nick Cameron	-2/+5

2016-01-15	Rollup merge of #30787 - nikomatsakis:future-incompatible-lint, r=brson	Manish Goregaokar	-0/+18
	There is now more structure to the report, so that you can specify e.g. an RFC/PR/issue number and other explanatory details. Example message: ``` type-parameter-invalid-lint.rs:14:8: 14:9 error: defaults for type parameters are only allowed on type definitions, like `struct` or `enum` type-parameter-invalid-lint.rs:14 fn avg<T=i32>(_: T) {} ^ type-parameter-invalid-lint.rs:14:8: 14:9 warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! type-parameter-invalid-lint.rs:14:8: 14:9 note: for more information, see PR 30742 <https://github.com/rust-lang/rust/pull/30724> type-parameter-invalid-lint.rs:11:9: 11:28 note: lint level defined here type-parameter-invalid-lint.rs:11 #![deny(future_incompatible)] ^~~~~~~~~~~~~~~~~~~ error: aborting due to previous error ``` r? @brson I would really like feedback also on the specific messages! Fixes #30746
2016-01-15	Add a test	Nick Cameron	-1/+1
	And fix bustage in make check
2016-01-15	Implement JSON error emission	Nick Cameron	-27/+210
	[breaking-change] syntax::errors::Handler::new has been renamed to with_tty_emitter Many functions which used to take a syntax::errors::ColorConfig, now take a rustc::session::config::ErrorOutputType. If you previously used ColorConfig::Auto as a default, you should now use ErrorOutputType::default().