-
Notifications
You must be signed in to change notification settings - Fork 166
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
Initial setup for test_gruntz #2423
Conversation
We have the ASR correctly in place (I think so). Pasting the whole ASR below. Would be great if somebody could verify it !
|
There are few things we need to discuss though. Also I'll give some context for anyone who would like to understand more (maybe cc @Thirumalai-Shaktivel @Shaikh-Ubaid )
To start with I think we might only be interested in capturing the mrv (most rapidly varying) subexpression which in our case is A most rapidly varying subexpression for an expression can be thought of a subexpression that grows the most rapidly in the expression. The general order would be
|
Does the test that you added work? If so, let's register it. If not, let's also add a test that fails in master, but now works. |
These are the errors I am getting through both the concerned backends
|
We could also actually start with something like the This would change the example to be a bit more easier. Something like this I reckon
So we could deal with something like |
Perfect. Yes, start with something that works. Then report issues for features that we need, and we'll keep fixing them, one by one, and iteratively improve the capability. |
To get started, instead of |
Closing as this was addressed through #2437 |
This is the first piece of code that we should support through LPython.