Skip to content
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 a heuristic for picking a copy method for Scala 3, when multiple are found #257

Merged
merged 2 commits into from
Nov 29, 2024

Conversation

KacperFKorban
Copy link
Collaborator

closes #256


// TODO: Would be nice to be able to handle this case. Based on the types, it
// is obvious, that the explicit copy should be picked, but I'm not sure if we
// can get that information
Copy link
Member

Choose a reason for hiding this comment

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

the type would need to be explicitly provided to modify, such as .modify[Char] I guess? but that's another feature

@adamw adamw merged commit d0a4712 into master Nov 29, 2024
4 checks passed
@adamw adamw deleted the fix-i256 branch November 29, 2024 15:33
@adamw
Copy link
Member

adamw commented Nov 29, 2024

Thanks for the fix!

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.

1.9.8 regression: copy with different signature than constructor produces error
2 participants