diff options
| author | Zack M. Davis <code@zackmdavis.net> | 2018-06-30 20:22:19 -0700 |
|---|---|---|
| committer | Zack M. Davis <code@zackmdavis.net> | 2018-06-30 22:20:28 -0700 |
| commit | 9df9c9df7bdcd688bcad9e91b9e2669f01d9f858 (patch) | |
| tree | 285a0144a736bc9b26f79873360a3ed9a2a18d6d /src/test/incremental/thinlto | |
| parent | 33b40f56792f0ed198b79818891634275cb8168e (diff) | |
| download | rust-9df9c9df7bdcd688bcad9e91b9e2669f01d9f858.tar.gz rust-9df9c9df7bdcd688bcad9e91b9e2669f01d9f858.zip | |
choose a less arbitrary span when parsing the empty visibility modifier
Visibility spans were added to the AST in #47799 (d6bdf296) as a `Spanned<_>`—which means that we need to choose a span even in the case of inherited visibility (what you get when there's no `pub` &c. keyword at all). That initial implementation's choice is pretty counterintuitive, which could matter if we want to use it as a site to suggest inserting a visibility modifier, &c. (The phrase "Schelling span" in the comment is meant in analogy to the game-theoretic concept of a "Schelling point", a value that is chosen simply because it's what one can expect to agree upon with other agents in the absence of explicit coördination.)
Diffstat (limited to 'src/test/incremental/thinlto')
0 files changed, 0 insertions, 0 deletions
