-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Fix nested hook call #18
Conversation
a580977
to
2610460
Compare
I'm thinking right now if we can scan the expression ahead of time and check if it has a hook call, opting-out of optimization, much like I feel like partial optimization is too complex for now. |
Yeah. I have noticed that, too. And that's exactly why I have converted the PR to the draft. I am trying a different approach (which I haven't pushed yet!) to address the fix. |
@lxsmnsyc I have refactored the bailout: |
@SukkaW I don't think this covers everything yet. A correct implementation is really difficult so I guess I would discourage you on doing that for now. A check like |
I have implemented |
This looks great! Thank you. I'll expand from your work. |
@lxsmnsyc My next PR will focus on merging |
@SukkaW You probably shouldn't. This is fine for 0.5.0. I have a plan for 0.6.0 to properly merge this all. |
The PR continues from #15.
The PR fixes these:
The PR handles a lot more nested hook call cases. The unit test case is also added.