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.

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

fix: don't panic in map range if assigned value is _ #1625

Merged
merged 1 commit into from
Apr 25, 2024

Conversation

mvertes
Copy link
Member

@mvertes mvertes commented Apr 25, 2024

Ensure that the code generated for for s, _ = range ... is the same as for s = range ....

Fixes #1622.

Ensure that the code generated for `for s, _ = range ...`
is the same as `for s = range ...`.

Fixes 1622.
@mvertes mvertes added bug Something isn't working area/core labels Apr 25, 2024
Copy link
Contributor

@ldez ldez left a comment

Choose a reason for hiding this comment

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

LGTM

@ldez ldez added this to the v0.16.x milestone Apr 25, 2024
@traefiker traefiker merged commit c828692 into traefik:master Apr 25, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/core bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

crash when iterator is nil in rangeMap
3 participants