-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Improvement in satask #17144
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
Improvement in satask #17144
Conversation
(note: tautology corner cases handled incorrectly)
|
✅ Hi, I am the SymPy bot (v147). I'm here to help you write a release notes entry. Please read the guide on how to write release notes. Your release notes are in good order. Here is what the release notes will look like:
This will be added to https://github.com/sympy/sympy/wiki/Release-Notes-for-1.5. Note: This comment will be updated with the latest check if you edit the pull request. You need to reload the page to see it. Click here to see the pull request description that was parsed.
Update The release notes on the wiki have been updated. |
|
Looks promising! However, since you base it on #11789 you should include those commits here (with correct authorship). Not sure how to go that in an easy way though, but maybe someone else knows. |
|
Not sure that all of these are from assumptions, but many are: Nice! |
Codecov Report
@@ Coverage Diff @@
## master #17144 +/- ##
=============================================
+ Coverage 74.487% 74.784% +0.296%
=============================================
Files 623 627 +4
Lines 161339 163574 +2235
Branches 37863 38629 +766
=============================================
+ Hits 120178 122328 +2150
- Misses 35833 35882 +49
- Partials 5328 5364 +36 |
|
@ShubhamKJha this looks like it will be useful but you need to fix the attribution of the commits. The way I would do this is to start a new branch as a copy of the old PR (with previous author information intact), rebase that on current master, then apply my changes on top. |
|
ping @asmeurer, @oscarbenjamin, @jksuom does it need further edits? Any other features (including a good strategy for the early encoding of literals) can be implemented in future PRs, since that will require some refactoring of code at various levels. |
I expect that might even be faster than doing |
|
ping @asmeurer @oscarbenjamin @jksuom is it now good enough to merge? |
|
This looks good to me. |
…d to prime and composite
|
The failing test seems to be unrelated to the PR here. Can anyone restart tests? |
|
Restart does not help. It seems that other pulls are also failing with an error in lambdify. |
|
Ok, the tests are passing. Ping @jksuom @oscarbenjamin, this can be merged now. |
|
Thanks, I also think that this can be merged. |
|
Thanks @ShubhamKJha (and@rlamy )! Great to see some speed-ups! (@ShubhamKJha if you are not bored with this topic yet, feel free to remove the slow-marks for the no longer slow tests in another PR. These are probably the candidates. ) |
|
Ah yes that definitely needs to be done, I forgot about that. |
|
slow-markers are removed in #17367 |
References to other Issues or PRs
Built over #11789.
A lot of time in the execution of
sataskis wasted in unnecessary creation ofAndandOrobjects. This PR tries to remove these intermediate steps.The current results in performance:
Brief description of what is fixed or changed
Other comments
Todos:
askmodule.LiteralsRelease Notes
cnf.pyto handle logical computations using low-level Python built-ins.