Felix S. Klock II 2646663b5a Put in -Z continue-parse-after-error ... 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-30 22:23:48 +02:00
..
Cargo.toml	bootstrap: Add a bunch of Cargo.toml files	2016-02-11 11:12:32 -08:00
driver.rs	Put in -Z continue-parse-after-error	2016-03-30 22:23:48 +02:00
lib.rs	sprinkle feature gates here and there	2016-03-22 22:02:47 -05:00
pretty.rs	try! -> ?	2016-03-22 22:01:37 -05:00
target_features.rs	Rustfmting librustc_driver.	2015-11-10 20:48:44 +00:00
test.rs	Auto merge of #30652 - aturon:specialization, r=nikomatsakis	2016-03-14 17:55:41 -07:00