-
Notifications
You must be signed in to change notification settings - Fork 43
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
Issue: Version 0.4.1 creates Type Exception on getOrElse #95
Comments
@SandroMaglione Can you elaborate what the issue exactly was? I tried to understand the PR but it just seems to change dependency versions. |
@ju851zel you can read details in #92 The issue was with introducing a |
well, it's not fixed. i got My issue was next: workaround is Option extension: similar problem with Option.toIOOption |
I noticed when using 0.4.1 in contrast to 0.4.0 a type exception is thrown when using
getOrElse
onOption
.The code responsible for the error is:
Is this a known issue? Downgrading to Version
0.4.0
from0.4.1
works.The text was updated successfully, but these errors were encountered: