diff options
| author | Mazdak Farrokhzad <twingoow@gmail.com> | 2019-08-14 22:56:25 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-08-14 22:56:25 +0200 |
| commit | 409df9b530d0aaac7e0de5cfb652d847eedeae30 (patch) | |
| tree | a9a2cae18938c9931057cd3860af8cf4bf5da959 /src/libsyntax/parse/parser | |
| parent | 02e2a57f262256fda9a8e3c89cfb18fe6b64ee01 (diff) | |
| parent | 376636e51719588edba82fc284328e14ce1f2d74 (diff) | |
| download | rust-409df9b530d0aaac7e0de5cfb652d847eedeae30.tar.gz rust-409df9b530d0aaac7e0de5cfb652d847eedeae30.zip | |
Rollup merge of #63528 - petrochenkov:anyany, r=estebank
syntax: Remove `DummyResult::expr_only` The effect is that if a built-in macro both returns an erroneous AST fragment and is used in unexpected position, then the incorrect position error won't be reported. This combination of two errors should be rare and isn't worth an extra field that makes people ask questions in comments. (There wasn't even a test making sure it worked.) Addresses https://github.com/rust-lang/rust/pull/63468#discussion_r313504644 r? @estebank
Diffstat (limited to 'src/libsyntax/parse/parser')
0 files changed, 0 insertions, 0 deletions