-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Reconsider overloading in NonEmptyVector #1204
Comments
👍 on removing the overloading as a general principle. Also, having a value class would be useful in specific use cases. The syntax is still useful for working with As an aside, with regard to value classes, it is worth bearing in mind that, as I understand at least, invoking any general code that involves summoning an instance would negate the benefit of the value class. i.e. summoning the |
Make NonEmptyVector a value class. #1204
Believe this should be resolved by #1212 |
Currently NonEmptyVector has overloaded
concat
and++
methods supporting bothNonEmptyVector
andVector
as the arguments.In general I'm a bit skeptical about overloading. In this specific case the main downside I see is that it prevents us from turning
NonEmptyVector
into a value class (which seems like it might be an otherwise reasonable thing to do).What do people think?
The text was updated successfully, but these errors were encountered: