Skip to content

Conversation

@psteinroe
Copy link
Collaborator

No description provided.

Copy link
Collaborator

@juleswritescode juleswritescode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nur 'n Nit 👍

}
}

/// Look ahead to the next relevant token *after the next token*
Copy link
Collaborator

@juleswritescode juleswritescode Mar 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Der Kommentar innerhalb der ** ist n bisschen confusing, es ist zwar under the hood next_pos + 1 aber für clients der API im Prinzip current + 1, oder? So liest es sich unten jedenfalls bei dem Ordinality check

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah it's hard to grasp because if you call peek(), the look ahead will basically return the next after peek 😅 what would you suggest as a comment?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

vllt. einfach /// Look ahead to the next relevant token, fühlt sich für mich verständlich an…
.peek() könnte auch current() sein glaube ich?

@psteinroe psteinroe merged commit a597279 into main Mar 14, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants