-
Notifications
You must be signed in to change notification settings - Fork 39
sigmatch: fix missing conversion for varargs containers #1627
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
Merged
zerbina
merged 3 commits into
nim-works:devel
from
zerbina:sigmatch-fix-missing-varargs-conversion
Oct 5, 2025
Merged
sigmatch: fix missing conversion for varargs containers #1627
zerbina
merged 3 commits into
nim-works:devel
from
zerbina:sigmatch-fix-missing-varargs-conversion
Oct 5, 2025
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Summary ======= Fix an internal-only problem with `sigmatch` handling of named parameters in conjunction with `varargs`. Details ======= Unlike for unnamed parameters, the implicit array construction created when using named parameters for passing a single value to a `varargs` parameter was not wrapped in a to-varargs conversion, nor was the type marked as being a varargs container (via the `tfVarargs` flag). This caused no downstream issues so far, as all three code generators handle the necessary run-time conversion themselves, but it's still incorrect.
saem
approved these changes
Oct 3, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice, I ran into this bug when reworking varargs/dispatch.
/merge |
Merge requested by: @zerbina Contents after the first section break of the PR description has been removed and preserved below:
|
github-merge-queue bot
pushed a commit
that referenced
this pull request
Oct 4, 2025
## Summary Fix an internal-only problem with `sigmatch` handling of named parameters in conjunction with `varargs`. ## Details Unlike for unnamed parameters, the implicit array construction created when using named parameters for passing a single value to a `varargs` parameter was not wrapped in a to-varargs conversion, nor was the type marked as being a varargs container (via the `tfVarargs` flag). This caused no downstream issues so far, as all three code generators handle the necessary run-time conversion themselves, but it's still incorrect.
/merge |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fix an internal-only problem with
sigmatch
handling of namedparameters in conjunction with
varargs
.Details
Unlike for unnamed parameters, the implicit array construction created
when using named parameters for passing a single value to a
varargs
parameter was not wrapped in a to-varargs conversion, nor was the type
marked as being a varargs container (via the
tfVarargs
flag).This caused no downstream issues so far, as all three code generators
handle the necessary run-time conversion themselves, but it's
still incorrect.