diff options
| author | bors <bors@rust-lang.org> | 2018-04-20 05:34:17 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2018-04-20 05:34:17 +0000 |
| commit | 257d43d0d580dc5e92a4aa4bebbd2bf5f04bbcae (patch) | |
| tree | ee6b6445d219acb464dccabf95db51fb66526f50 /src/test/incremental/thinlto | |
| parent | f4a3df1f76509b9dd7380db7ce60bd67bc5d5e7e (diff) | |
| parent | e9348738fca8c88dca6e343702eaa12ffc8df34c (diff) | |
| download | rust-257d43d0d580dc5e92a4aa4bebbd2bf5f04bbcae.tar.gz rust-257d43d0d580dc5e92a4aa4bebbd2bf5f04bbcae.zip | |
Auto merge of #50069 - alexcrichton:fix-proc-macro, r=nrc
proc_macro: Stay on the "use the cache" path more Discovered in #50061 we're falling off the "happy path" of using a stringified token stream more often than we should. This was due to the fact that a user-written token like `0xf` is equality-different from the stringified token of `15` (despite being semantically equivalent). This patch updates the call to `eq_unspanned` with an even more awful solution, `probably_equal_for_proc_macro`, which ignores the value of each token and basically only compares the structure of the token stream, assuming that the AST doesn't change just one token at a time. While this is a step towards fixing #50061 there is still one regression from #49154 which needs to be fixed.
Diffstat (limited to 'src/test/incremental/thinlto')
0 files changed, 0 insertions, 0 deletions
