Skip to content

Issues with determining posistion of null values #34

Closed Answered by Ethiraric
ClausHolbechArista asked this question in Q&A
Discussion options

You must be logged in to vote

There is much room for improvement with regard to spans. As of now, I'm more trying to focus on performance and avoiding to always have to reallocate objects.

The Null case is an interesting one. I suppose it stems from the fact that we cannot know until we reach the next token that there is a Null value, at which time the position in the parser is already set to said next token. Explicit Null values should have their Span set properly I assume?

I don't want to take too much of your time, but a #[test] for the expected Markers on Null nodes would help a lot.

The only thing I can think of as a suggestion aside from the custom EventReceiver would be a pull request :( I don't think there is …

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@ClausHolbechArista
Comment options

Answer selected by ClausHolbechArista
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants