Skip to content

Conversation

@bishabosha
Copy link
Member

As mentioned in #20267, the new desugaring from #20497 seems to fix the issue

fixes #20267

Copy link
Contributor

@EugeneFlesselle EugeneFlesselle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As mentioned in the original issue, it's unfortunate the type level ops don't work well with precise types

But avoiding those problems for named tuples is definitely an improvement 👍

@bishabosha bishabosha merged commit cfc51b0 into scala:main Jun 2, 2024
@bishabosha bishabosha deleted the named-tuples-i20267 branch June 2, 2024 18:23
@Kordyjan Kordyjan added this to the 3.5.1 milestone Jul 3, 2024
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.

Named Tuples don't propagate singleton types as widely as tuples

3 participants