about summary refs log tree commit diff
path: root/src/test/rustdoc-js-std/string-from_ut.js
diff options
context:
space:
mode:
authorRalf Jung <post@ralfj.de>2020-05-16 19:46:31 +0200
committerGitHub <noreply@github.com>2020-05-16 19:46:31 +0200
commit8bba1b758916d012a09463c4aade5750cd482f80 (patch)
tree1dde4ae27d6efdde7ccfd48787e65c1b31af30d3 /src/test/rustdoc-js-std/string-from_ut.js
parentb381ea8abb278e42c3f157440fd1bd2af6c7782d (diff)
parentff9a9ed37c5e0b41c083c92aa908b1277e97ef09 (diff)
downloadrust-8bba1b758916d012a09463c4aade5750cd482f80.tar.gz
rust-8bba1b758916d012a09463c4aade5750cd482f80.zip
Rollup merge of #72047 - Julian-Wollersberger:literal_error_reporting_cleanup, r=petrochenkov
Literal error reporting cleanup

While doing some performance work, I noticed some code duplication in `librustc_parser/lexer/mod.rs`, so I cleaned it up.

This PR is probably best reviewed commit by commit.

I'm not sure what the API stability practices for `librustc_lexer` are. Four public methods in `unescape.rs` can be removed, but two are used by clippy, so I left them in for now.
I could open a PR for Rust-Analyzer when this one lands.

But how do I open a PR for clippy? (Git submodules are frustrating to work with)
Diffstat (limited to 'src/test/rustdoc-js-std/string-from_ut.js')
0 files changed, 0 insertions, 0 deletions