-
-
Notifications
You must be signed in to change notification settings - Fork 619
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
Deprecate methods of Value #2450
Open
13 of 28 tasks
Comments
Hello, Why the interface Value is deprecated now ? |
It is the development branch and not released. I had in mind to re-implement big parts of Vavr. But I do not have the time to do that. I will undeprecate all the things by time. It is important not to break the existing Vavr version. |
Thank you, i cloned the repo to understand the code and then try to contribute. |
Thanks |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Mark Value methods asValue will not be deprecated. My initial plan was to introduce io.vavr.Iterable instead but that is not a good idea. The name would be ambiguous because there exists java.lang.Iterable. Instead we will just deprecate and move the Value methods mentioned below.@Deprecated
getOrNull()
resp.orNull()
does not make sense in the presence of primitive generics. E.g. having anOption<int> opt
, callingint i = opt.getOrNull()
would be fatal.The text was updated successfully, but these errors were encountered: