Avoid NoPosition.start in Scaladoc warning #10721
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some docs for synthetic symbols derived from
library-aux
sources have no position (for some reason).Also for some reason, operations on position are brittle instead of safe. I'd expect to map a position such that the degenerate position remains safely degenerate instead of throwing (which helps no one). After solving
NoSymbol has no owner
, they ought to have tackledNoPosition has no start
.This commit just patches the warning not to do position arithmetic on NoPosition.
It requires restarr to work for the OP.
Edit: this commit also doesn't address "doc variable resolution in code block".
Edit: Fixes scala/bug#12964