-
Notifications
You must be signed in to change notification settings - Fork 437
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
["Request"] Investigate providing type hints using DeprecationLevel.ERROR #2838
Comments
I'll take a stab at this in |
Yes, that is most likely going to occur but in those case need to explicitly call |
What version are you currently using?
1.x.x
What would you like to see?
Sometimes it's not clear why
Either<Throwable, Int>
cannot bebind
insideeither<String, A> { }
,and similarly with other data types that don't match the logical failure channel type.
Based on some discussions on Twitter, and Slack we discovered that you can leverage
DeprecationLevel.ERROR
to provide hints to the user, to clarify why the signature results in aERROR
.We can on a per type/signature basis provide better error messages to the user. I.e.
https://twitter.com/vergauwen_simon/status/1578047840227557379?s=20&t=REup7C6kEet76dtI66gUIQ
https://kotlinlang.slack.com/archives/C5UPMM0A0/p1665068590923969
The text was updated successfully, but these errors were encountered: