When returning a SyntaxReference, also return the SyntaxSet that contains it #1776
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.
Here comes what I think will be the most controversial change on the #951 journey, because it has the highest impact on the bat-as-a-library API. Let me know what you think about it.
To improve startup performance, we will later load smaller
SyntaxSet
s instead of one giant one. However, the current API assumes only oneSyntaxSet
is ever used, and that that implicitly is theSyntaxSet
from which returnedSyntaxReference
s comes.This change changes the API to reflect that
SyntaxSet
andSyntaxReference
are tightly coupled, and enables the use of severalSyntaxSet
.I think it will make sense to add a helper method to reduce the boilerplate a bit, but I would like to get early feedback on the change itself before I do that.