-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Deny (by default) transmuting from fn item types to pointer-sized types. #34923
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
r? @Aatch (rust_highfive has picked a reviewer for you, use r? to override) |
@nikomatsakis This supersedes #34198, for now. I've started a three-way crater build on both PRs, to measure the impact for both changes. |
Argh, the report came out half-baked. All of the cases I checked out are just timeouts, while updating the registry. cc @brson |
d04f81b
to
7de83f0
Compare
The good crater report shows 3 regressions, I've also done a crater run for #34198, for which the report shows 3 more regressions (because |
cc @rust-lang/compiler @rust-lang/core -- another question of making warnings into a hard error, though in this case we opted for a more gradual approach by making the lint become Deny By Default, since the impact of this change was initially large. @eddyb's measurements show 3 regressions:
My vote is let's go for it. |
🍈 (I'm in favor) |
👍 |
@nikomatsakis Are we go? |
@wycats any updates here? Do you have examples where you think the lint is failing to fire or be reported? |
OK, I think we should land this. It's not irreversible. |
@bors r+ |
📌 Commit 7de83f0 has been approved by |
Deny (by default) transmuting from fn item types to pointer-sized types. This sets the #19925 lint (transmute from zero-sized fn item type) to `deny` by default. Technically a `[breaking-change]`, but will not affect dependent crates because of `--cap-lints`.
This sets the #19925 lint (transmute from zero-sized fn item type) to
deny
by default.Technically a
[breaking-change]
, but will not affect dependent crates because of--cap-lints
.