You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 21, 2018. It is now read-only.
This is giving me a bit of a headache. I checked how roslyn does it: They tokenize a single string token (like we do now), then create a fresh scanner/parser to break it up into multiple tokens, which themselves contain parsed data in the case of expressions, or something like that.
For starters, I'm having architectural issues because emitters can't really create new parsers as that would require them to refer to themselves recursively. This could probably be solved in some way, but I'm not sure how to properly do it.
Then there's the problem of the token list. By the time the original string token is emitted, it is already part of the token list. We would have to replace it with the result of the recursive parsing operation.
Overall, this seems very complicated. It might be a better idea to leave it unchanged for now and provide an entry point "interpolated_string". The result can then be combined through the incremental parsing API that we hopefully manage to get right at some point.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now, it's all just one token:
The text was updated successfully, but these errors were encountered: