diff options
| author | bors <bors@rust-lang.org> | 2023-01-02 13:07:42 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-01-02 13:07:42 +0000 |
| commit | 790759fb11164676593f40e85e346cea551bcc4a (patch) | |
| tree | ee1dadbb0379b82ca910d335c0620561c63abe8b /src/test/codegen/src-hash-algorithm | |
| parent | e986de0b288b1544349f20a445df25e6265594b4 (diff) | |
| parent | a7d411425c10261bd1535d0e98cbe2e7181b9553 (diff) | |
| download | rust-790759fb11164676593f40e85e346cea551bcc4a.tar.gz rust-790759fb11164676593f40e85e346cea551bcc4a.zip | |
Auto merge of #13854 - lowr:fix/mbe-glue-punct, r=Veykril
Support multi-character punct tokens in MBE Fixes #11497 In the context of MBE, consecutive puncts are parsed as multi-character punct tokens whenever possible. For example, `:::` is parsed as ``[Punct(`::`), Punct(`:`)]`` and shouldn't get matched to patterns like `: : :` or `: ::`. We have implemented this behavior only for when we match puncts against `tt` fragments, but not when we match puncts literally. This PR extracts the multi-character punct handling procedure into a separate method and extends its support for literal matching. For good measure, this PR adds support for `<-` token, which is still [considered as one token in rustc](https://github.com/rust-lang/rust/blob/e3961864075eaa9e855e5eec6b4f148029684539/compiler/rustc_ast/src/token.rs#L249) despite the placement syntax having been removed.
Diffstat (limited to 'src/test/codegen/src-hash-algorithm')
0 files changed, 0 insertions, 0 deletions