Move vavr.control.Try,vavr.control.Either,vavr.control.Option to `vavr` package.

[He-Pin]

refs:scala/bug#11268

[danieldietrich]

Thanks for the suggestion.
Moving things around might be 'foolish consistency'. It will break code out there.
The only benefit is grouping things that belong together - we already do that!
Is it worth to break existing applications? (I don't think so)

When will Scala move Try and Either?

[He-Pin]

@danieldietrich I think they will move it in 2.14, it's planed in 2.13 but you know:)

[danieldietrich]

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.

[He-Pin]

I can only say if that will be done, they should be done in 1.0, as they are the most basic types:)
There is no type alias in Java so, I don't know.

[danieldietrich]

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.

[He-Pin]

@danieldietrich FYI: scala/scala#7425 ,I think this should be done in 1.0 if you decided to .