Fix starting range in REPLCompletions #49547
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.
The new completion for
var"
fields (#49294) failed when thevar"
was at the end of the completion query, e.g. inWeirdNames().var"
. This is because we have the following behavior:REPLCompletions attempt to find
.
starting after thevar"
, which in this case is at the end of the string. Of course, the index was probably off by one anyway, becausewe didn't want to match
var".
, but nevertheless, I find this behavior surprising (ref also [1]).For now, fix this by starting the search before the
var"
, but we may want to revisit thefindprev
behavior also.[1] https://github.com/JuliaLang/julia/pull/35742/files#r420945975