-
Notifications
You must be signed in to change notification settings - Fork 145
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
Add unsafe checks #1411
Comments
What do you mean with a layout constrained field? A field of a packed struct? Or a field of a type with the |
I'm referring to these two unsafe operations which seems to be triggered only in some cases like this one I didn't look much into it, I had just read your comment on #182 and assumed this had to do with |
I see. In that case I have another item to add to the list:
|
Thank you! Adding it to the list to make sure I don't miss it |
1711: unsafe: check use of `target_feature` attribute r=CohenArthur a=snprajwal The `target_feature` attribute is for conditional compilation and may or may not compile on all platforms. Using it requires an unsafe function or block. Addresses #1411 Co-authored-by: Prajwal S N <prajwalnadig21@gmail.com>
asm!()
in safe contexts #1569#[target(feature)]
attributerustc_layout_scalar_valid_range
attributeI believe the last two are related to the Freeze lang item which we do not support yet.
From @bjorn3:
The text was updated successfully, but these errors were encountered: