Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feature: Allow peek parameter for opcode dispatch IDL #5

Open
mmastrac opened this issue Jun 28, 2021 · 0 comments
Open

Feature: Allow peek parameter for opcode dispatch IDL #5

mmastrac opened this issue Jun 28, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@mmastrac
Copy link
Owner

DUP and ITERATOR_NEXT could be made much cleaner using a peek parameter for opcode dispatch. As it stands right now, DUP is handled manually and ITERATOR_NEXT is forced to store its variable in a local (disallowing alternative setting forms that Python allows like for a[3] in x {.
@mmastrac mmastrac added the enhancement New feature or request label Jun 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mmastrac