about summary refs log tree commit diff
path: root/src/libsyntax/diagnostics/macros.rs
AgeCommit message (Collapse)AuthorLines
2020-01-08- remove syntax::{span_warn!, span_err!, span_fatal!. struct_err!}Mazdak Farrokhzad-169/+0
- remove syntax::{help!, span_help!, span_note!} - remove unused syntax::{struct_span_fatal, struct_span_err_or_warn!, span_err_or_warn!} - lintify check_for_bindings_named_same_as_variants + conflicting_repr_hints - inline syntax::{struct_span_warn!, diagnostic_used!} - stringify_error_code! -> error_code! & use it more. - find_plugin_registrar: de-fatalize an error - de-fatalize metadata errors - move type_error_struct! to rustc_typeck - struct_span_err! -> rustc_errors
2019-12-22Format the worldMark Rousskov-4/+4
2019-11-14Update to use new librustc_error_codes libraryGuillaume Gomez-23/+1
2019-09-05Replace diagnostic plugins with macro_rulesMark Rousskov-26/+29
2019-07-13Make `register_[long_]diagnostics` hygienicMatthew Jasper-4/+4
2018-12-25Remove licensesMark Rousskov-10/+0
2018-01-15Add error code for unstable feature errorsGuillaume Gomez-0/+8
2017-11-02Make the difference between lint codes and error codes explicitOliver Schneider-11/+54
2017-06-11Add E0609Guillaume Gomez-0/+11
2017-05-30Add new error codeGuillaume Gomez-0/+8
2016-05-02replace fileline_{help,note} with {help,note}Niko Matsakis-3/+3
The extra filename and line was mainly there to keep the indentation relative to the main snippet; now that this doesn't include filename/line-number as a prefix, it is distracted.
2015-12-30use structured errorsNick Cameron-8/+44
2015-08-12Introduce a "origin/cause" for new requirements (or bugfixes...) introduced ↵Niko Matsakis-0/+12
by RFC 1214, and issue a warning (and explanatory note) when we encounter such a thing.
2015-07-17Improve register_long_diagnostics macroGuillaume Gomez-0/+3
2015-07-16Improve register_diagnostics macroGuillaume Gomez-0/+3
2015-03-03Change span_help calls to fileline_help where appropriateIvan Radanov Ivanov-0/+7
2015-02-05cleanup: replace `as[_mut]_slice()` calls with deref coercionsJorge Aparicio-5/+5
2015-01-20Add some extended errors.Michael Sproul-0/+6
2015-01-20Make fatal errors work with codes, add to typeckBrian Anderson-0/+8
2015-01-05Stop using macro_escape as an inner attributeKeegan McAllister-2/+0
In preparation for the rename.
2014-12-18librustc: Always parse `macro!()`/`macro![]` as expressions if notPatrick Walton-15/+16
followed by a semicolon. This allows code like `vec![1i, 2, 3].len();` to work. This breaks code that uses macros as statements without putting semicolons after them, such as: fn main() { ... assert!(a == b) assert!(c == d) println(...); } It also breaks code that uses macros as items without semicolons: local_data_key!(foo) fn main() { println("hello world") } Add semicolons to fix this code. Those two examples can be fixed as follows: fn main() { ... assert!(a == b); assert!(c == d); println(...); } local_data_key!(foo); fn main() { println("hello world") } RFC #378. Closes #18635. [breaking-change]
2014-10-29Diagnostic: resolve bare fn in expected closuregamazeps-0/+7
Closes #15273 (I did not find how to get the identifier in the message :/) Also creates the span_help! macro associated with #18126
2014-07-19Register new snapshotsAlex Crichton-26/+0
2014-07-18Assign more diagnostic codesJakub Wieczorek-6/+6
2014-07-12Convert a first batch of diagnostics to have error codesJakub Wieczorek-0/+22
2014-07-11Add scaffolding for assigning alpha-numeric codes to rustc diagnosticsJakub Wieczorek-0/+51