Origin: internally expose possible input #3911
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bjaglin
reviewed
Aug 24, 2024
|
|
||
| private[meta] def retokenizeFor( | ||
| dialect: Dialect | ||
| )(implicit tokenize: Tokenize, tokenizerOptions: Option[TokenizerOptions]): Tokens = this match { |
There was a problem hiding this comment.
Suggested change
| )(implicit tokenize: Tokenize, tokenizerOptions: Option[TokenizerOptions]): Tokens = this match { | |
| )(implicit tokenize: Tokenize): Tokens = this match { |
|
|
||
| private[meta] def retokenize(implicit | ||
| tokenize: Tokenize, | ||
| dialect: Dialect, | ||
| tokenizerOptions: Option[TokenizerOptions] |
There was a problem hiding this comment.
Suggested change
| tokenizerOptions: Option[TokenizerOptions] |
| case Lit.String(value) => | ||
| val input = Input.VirtualFile("<InternalTrees.tokens>", value) | ||
| Tokens(Array(Constant.String(input, dialect, 0, value.length, value))) | ||
| case _ => implicitly[Tokenize].apply(textAsInput, dialect).get | ||
| case _ => tokenize(origin.inputOpt.getOrElse(textAsInput), dialect).get | ||
| } | ||
|
|
||
| private[meta] def textAsInput(implicit |
There was a problem hiding this comment.
not visible in the diff, but another implicit Option[TokenizerOptions] is captured - it's probably more correct to get it from the input just like above?
In InternalTree, use it to tokenize, before resorting to syntax parsing. Also, if that Input contained any TokenizerOptions, they would naturally be used.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In InternalTree, use it to tokenize, before resorting to syntax parsing. Also, if that Input contained any TokenizerOptions, they would naturally be used. Follow-on to #3786.