-
-
Notifications
You must be signed in to change notification settings - Fork 59
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
Start Operators with no meaning section #1171
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
# -*- coding: utf-8 -*- | ||
# Note: this will be redone soon to pull no-meaning operator information from operators.yml out | ||
# of the MathicsScanner project. | ||
""" | ||
Operators without Built-in Meanings | ||
|
||
Not all operators recognized by the Mathics3 are associated with functions that have built‐in meanings. | ||
You can use these operators as a way to build up your own notation within the Mathics3. | ||
""" | ||
|
||
from mathics.core.attributes import A_NO_ATTRIBUTES | ||
from mathics.core.builtin import BinaryOperator | ||
|
||
|
||
class Star(BinaryOperator): | ||
r""" | ||
Star <url> | ||
:WML link: | ||
https://reference.wolfram.com/language/ref/Star.html</url> | ||
|
||
<dl> | ||
<dt>'Star[$x$, $y$, ...]' | ||
<dd>displays $x$ ⋆ $y$ ⋆ ... | ||
</dl> | ||
|
||
>> Star[x, y, z] | ||
= x ⋆ y ⋆ z | ||
|
||
>> a \[Star] b | ||
= a ⋆ b | ||
""" | ||
|
||
attributes = A_NO_ATTRIBUTES | ||
default_formats = False # Don't use any default format rules. Instead, see below. | ||
formats = { | ||
(("InputForm", "OutputForm", "StandardForm"), "Star[args__]"): ( | ||
'Infix[{args}, "⋆"]' | ||
), | ||
} | ||
|
||
operator = "⋆" # \u22C6 | ||
summary_text = "star symbol" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
It would be OK if in the class definition, we use a Python string, if we convert it later into a Symbol. So, it would be a problem of
contribute
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 checked it out, and indeed
grouping
is used to build a Pythonstr
, that is parsed as a pattern object for defining formatting and boxing rules. So probably it is OK to keep is as a str.