fix panic in inlay hint computation when view anchor is out of bounds #6883
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.
Fixes the crash from this comment #6752 (comment)
Note that this crash is not the same crash that #6752 is about and was incorrectly reported there. The problem here is simply that
view.offset.anchor
was used directly withchar_to_line
, but the anchor can be out of bounds which causes a crash here. Everywhere else where the anchor is used we currently usedanchor.min(doc.len_char())
for that reason. This PR just adds that to the inlay hint computation too since we forgot about it there.