-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
IRB crash #104
Comments
This is because of #73 that will be addressed in dry-logic 2.0 |
Also see #99 - if there's anything we can do to workaround this for the time being, I'm more than happy to do it |
@solnic Thank you for response! |
@vladimirtemnikov yeah this is unfortunate. In other places people worked around it by just checking arity of the |
@solnic sounds great, I guess this conflict could wait a bit then. |
@vladimirtemnikov I just realized we can simply do this #105 |
@solnic elegant solution! ❤️ Didn't even think about this. |
@solnic did you have a target release date for 2.0? |
@kris 2023 Q1 |
This should work with dry-logic 1.5.0 now 🙂 |
@solnic Awesome! |
I'm hitting this issue dry-rb/dry-logic#104
I'm hitting this issue dry-rb/dry-logic#104
Can this be backported to any older versions of dry-logic? It would be helpful to have this fix on dry-logic 1.3.x |
Describe the bug
Hello.
Using dry-logic 1.4.0, irb 1.5.0.
As I mentioned in ruby/irb#455, a session crashes if irb's autocomplete feature is enabled.
To Reproduce
Type
AnyClass.new.
in console.Other details in irb issue link.
Expected behavior
No session crash.
The text was updated successfully, but these errors were encountered: