-
Notifications
You must be signed in to change notification settings - Fork 156
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
Refactor: Several Improvements #2160
Refactor: Several Improvements #2160
Conversation
4028404
to
ed22f82
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For a compiler like ours which is in fast pace development mode, I wouldn’t remove code which never gets triggered by the tests. Instead I would prefer adding tests which trigger that code. Its a time consuming process but that’s better than removing unused code because they might be having some important logic we might have written but missed to add tests for it (< 100% code coverage is very normal).
reference: Remove code that never gets triggered. Actually, it is not about the tests. The |
Ready. |
Can you send a PR to LFortran for this change in libasr as well? Let's see if it breaks anything there. |
Sure, please see lfortran/lfortran#1989. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that this is fine, it works in LFortran.
No description provided.