-
-
Notifications
You must be signed in to change notification settings - Fork 646
Move vavr.control.Try,vavr.control.Either,vavr.control.Option to vavr
package.
#2328
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
Comments
Thanks for the suggestion. When will Scala move Try and Either? |
@danieldietrich I think they will move it in 2.14, it's planed in 2.13 but you know:) |
The difference between Vavr and Scala is that scala have different packages for Option, Either and Try (scala and scala.util) and we have one package (io.vavr.control). Do you think it is worth to break backeard compatibility, by moving Option, Try and Either to io.vavr? I agree that these are our most basic types. |
I can only say if that will be done, they should be done in 1.0, as they are the most basic types:) |
Moving them from io.vavr.control to io.vavr will lock us forever from shipping controls as a separate module. I will think about it. It is not the most important task for now. I will focus on the collection interfaces next. We will decide it until 1.0 final. |
@danieldietrich FYI: scala/scala#7425 ,I think this should be done in 1.0 if you decided to . |
refs:scala/bug#11268
The text was updated successfully, but these errors were encountered: