-
Notifications
You must be signed in to change notification settings - Fork 158
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
Editorial: Improve consistency of mathematical conventions #2162
Editorial: Improve consistency of mathematical conventions #2162
Conversation
…tion `-` (U+002D HYPHEN-MINUS) rather than `−` (U+2212 MINUS SIGN) cf. tc39/ecma262#2730
`×` should be encoded as `×`
`≤` and `≥` should be encoded as `≤` and `≥`, respectively
`≠` should be encoded as `≠`
`∞` should be encoded as `∞`
Codecov Report
@@ Coverage Diff @@
## main #2162 +/- ##
=======================================
Coverage 90.03% 90.03%
=======================================
Files 19 19
Lines 10905 10905
Branches 1693 1693
=======================================
Hits 9818 9818
Misses 1073 1073
Partials 14 14
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
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 it's a bit silly that we have glyphs like 𝔽 written out, but character entities for things like ×
, and I think ECMA-262 made the wrong choice to prefer - (hyphen) over U+2212 (−
), but if this is the current convention then 🤷
I do expect the conventions to change at some point, but this provides alignment now (and will close an open issue when it lands). |
Fixes #1548
Ref tc39/ecma262#2730
-
(U+002D HYPHEN-MINUS) rather than−
(U+2212 MINUS SIGN)×
≤
/≥
≠
∞