Update Elixir tokenization of sigil modifiers #2806
Merged
Conversation
This file contains 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
|
Thank you!
Please see here #2807 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Elixir has syntax for custom string interpreters like
~r/regex/i. The trailing part is a set of modifiers, in this case making the regexp case-insensitive. The modifiers could only be lower and uppercase characters, but a recent change allows numbers too. See elixir-lang/elixir#11282.I also updated operators with the
**(power), which has been added recently.Sidenote: when building the website locally it always used the old version of tokenizers, I even tried resetting the repo, running install, release, build-website, simpleserver and it would still pick up the old version. Is there an option to build from local files?