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.
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
check object safety of generic constants #78365
check object safety of generic constants #78365
Changes from all commits
9dadcf8
0e419ef
8546a80
60bcc58
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Can you also add a test for this? That will need the const generics feature gate so you can have non-usize constants, but that's fine.
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.
we already check this,
[u8; bar::<Self>]
only fails because ofvisit_ty
as bar isConst { ty: fn bar with substs [Self], ct: ZST }
.If we did not add this
visit_ty
here we would never fail for constants, which took me a while to find outThere 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.
wait... what? as far as I can tell you only have
bar::<Self>()
, which is a constant ofusize
type. Even if its body contains other stuff.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.
yeah, meant
bar::<Self>()
. The issue here is thatbar::<Self>
is a ZST of typefn() -> usize { bar<Self> }
, so we have to look at the type of constants to see if they referenceSelf
. The value of a const cannot referenceSelf
afaikThere 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 get that, but I don't understand how the constant we are visiting is ever anything but a constant with
ty: usize
, where the constant's value may beUnevaluated(DefIdOfbar, [Self])
, but that value is essentially irrelevant for thevisit_ty
here. Or is this during the visiting of the MIR of theusize
typed constant? I don't think it ever is that, as the visitor we are currently talking about is visiting the signature of the functionThere 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.
So we are visiting
[u8; bar::<Self>()]
and then the abstract const for the array length which isSo
Self
is only mentioned in the type of the function object.During the visiting of the
AbstractConst
of the usize typed constantThere 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.
Oh, now I realize where my confusion is coming from. It's actually both!
So...
isn't possible, thus no
is possible either.