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.

Sign up for GitHub

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

Jump to bottom

Option2Iterable shouldn't be triggered when explicitly converting an Option to another collection type #570

Open
nigredo-tori opened this issue Feb 2, 2022 · 0 comments
Open

Option2Iterable shouldn't be triggered when explicitly converting an Option to another collection type #570

nigredo-tori opened this issue Feb 2, 2022 · 0 comments

Comments

@nigredo-tori
Copy link
Contributor

At the moment, expressions like option.toSet trigger the wart, requiring either suppression or weird workarounds like option.toList.toSet. In my opinion, the wart should ignore the implicit conversion when it is followed by .toSet or similar combinators.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nigredo-tori