-
-
Notifications
You must be signed in to change notification settings - Fork 56
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
Increased use of binary operator string values from JSON #1256
Conversation
1007725
to
d50a306
Compare
This should stay in draft mode until Mathics3/mathics-scanner#111 is merged. Then, I'll revert the CI testing from the operator-refactor-part1.5 branch and we can merge this. Getting operator information in better shape is a prerequisite for the next release. |
Note: after this PR we may have a few more binary operators; also postfix and prefix operators should be done as well. However just this part is major disruption in of itself, to warrant stopping here and doing the others other PRs. |
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.
LGTM
Mathics-scanner code is merged, so we'll now try with master. If this works, I will merge. And maybe we can continue with prefix/postifx operators. |
Also add one more type annotation
4787770
to
a9b0d00
Compare
Pick up binary operator string from enhanced Mathics-Scanner JSON operator tables.
For now, we have to limit to binary operators only.