-
Notifications
You must be signed in to change notification settings - Fork 236
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
User-created keywords #3593
Comments
As pointed out in the comments of #3584, this also works but messes up things:
|
Some relevant remarks:
so the difference is made using parsing information.
|
I intend to rewrite |
This was referenced Nov 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Following #3584, compare
Why the difference? because an arbitrary list of symbols has been declared as a keyword (something that I'd rather call a binary operator, but sadly the word
Binary
is used for something completely different in M2. I digress.), i.e., something that's used like this:But realistically most users are never going to use
⧢
so why this symbol rather than another?I think it'd make much more sense for users/packages to be able to define their own Keywords. Then the Core should stick to a minimal set of Keywords.
Incidentally note that
new Keyword from ×
will not produce an error (though currently, it probably should, since the result is not what you would expect).The text was updated successfully, but these errors were encountered: