-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
don't special case DefKind::Ctor
in encoding
#94252
Conversation
☔ The latest upstream changes (presumably #94129) made this pull request unmergeable. Please resolve the merge conflicts. |
This comment has been minimized.
This comment has been minimized.
a1fd42e
to
ae45e8a
Compare
I had originally introduced this to avoid a change in diagnostics. It don't expect any other consequence. |
📌 Commit ae45e8a has been approved by |
⌛ Testing commit ae45e8a with merge cc14ae0823a1dd79fe26dd4a41f586d8c664894d... |
💔 Test failed - checks-actions |
crates.io was down ^^ @bors retry |
…askrgr Rollup of 7 pull requests Successful merges: - rust-lang#93845 (Remove in band lifetimes) - rust-lang#94155 (Extend toggle GUI test a bit) - rust-lang#94252 (don't special case `DefKind::Ctor` in encoding) - rust-lang#94305 (Remove an unnecessary restriction in `dest_prop`) - rust-lang#94343 (Miri fn ptr check: don't use conservative null check) - rust-lang#94344 (diagnostic: suggest parens when users want logical ops, but get closures) - rust-lang#94352 (Fix SGX docs build) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
considering that we still use
DefKind::Ctor
for these inRes
, this seems weird and definitely felt like a bug when encountering it while working on #89862.r? @cjgillot