Skip to content

Conversation

@ChayimFriedman2
Copy link
Contributor

And remove it when needed, the opposite of what was previously, where we stored without a tuple and tupled for the solver (because it requires that).

Because this is what rustc does, and generally, the closer we follow rustc, the easier our lives become.

The weird name signature_unclosure() also comes from rustc.

As an aside: we need to fix our coercion due to rust-lang/rust#148602.

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Dec 25, 2025
And remove it when needed, the opposite of what was previously, where we stored without a tuple and tupled for the solver (because it requires that).

Because this is what rustc does, and generally, the closer we follow rustc, the easier our lives become.

The weird name `signature_unclosure()` also comes from rustc.
@Veykril Veykril added this pull request to the merge queue Dec 26, 2025
Merged via the queue into rust-lang:master with commit c83c1a5 Dec 26, 2025
15 checks passed
@rustbot rustbot removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Dec 26, 2025
@ChayimFriedman2 ChayimFriedman2 deleted the tupled-closure branch December 26, 2025 11:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants