-
Notifications
You must be signed in to change notification settings - Fork 13.4k
use cfg_select!
to select the right VaListImpl
definition
#141361
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
Open
folkertdev
wants to merge
1
commit into
rust-lang:master
Choose a base branch
from
folkertdev:varargs-cfg
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
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.
I'm confused by this implementation that is used when we don't know the layout of
va_list
(the_ => { ... }
case in thecfg_match!
above). It is inconsistent with the others.Could we not have
&'a mut VaListImpl<'f>
here like above, and make theVaListImpl
a ZST containing just the invariance marker?Is that fallback implementation even meaningful?
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.
Ok no, after reading a bit more there are just two approaches
va_list
is just an opaque pointer (probably just the next variadic argument on the stack, though it's opaque so we can't know)va_list
is some sort of struct. It looks like this is used when registers are also at play for passing variadic argumentsThese two approaches are captured by the two different ways of representing
VaList
. I added a comment with some of that information, in particular #56599 had some useful info.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.
That does raise the question: what is
VaList
for? it has no methods of its own, so I don't see its purpose.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.
VaList
is supposed to be ABI compatible with C'sva_list
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.
Yes, I was confused by the C definition, until I rediscovered that nasty thing where
sizeof
in C is not the same assize_of
in rust: for arrays,sizeof
gives the length of the array, though it is really used/passed as a pointer type.Anyway, #44930 (comment) has an updated design for this api, which keeps
VaListImpl
private.