Hyeseong Kim

> Should we even allow this? In the definition of the exotic identifier.. yes. As they are legit identifier names in JS 😅

Hmm, weird. I thought any Unicode sequences were allowed in identifier names since ES6. https://mathiasbynens.be/notes/javascript-identifiers-es6 And saw some toy projects like https://github.com/Thomas101/emoji-js I can still find records saying it was...

I found specific Unicode properties, `ID_Start` and `ID_Continue`, to restrict the range of Unicode in identifier names. - https://tc39.es/ecma262/#prod-IdentifierStart - https://github.com/dtolnay/unicode-ident - https://github.com/oxc-project/unicode-id-start

Not sure its perf and size, but maybe we can check in the parser https://github.com/dbuenzli/uucp/blob/master/src/uucp__id.ml

We can support custom infixes by changing the int type fallback to be done indirectly with implicit `open Infix`

Checking rhs type in inference adds quite a bit of complexity. I wonder if there are any use cases for this. If not, it makes sense to consider checking only...

> @cometkim you waiting on anything from any of us on this one? No, I just took a break from coding over the Korean holidays.

It now works for basic arithmetic operators

> > 2. **`*`** (`%mul`): While unusual for most data types, `*` is often supported for strings in some languages (like Python) for repetition. For example, `"abc" * 3` results...

I haven't added `char` here (yet?), but it would be confusing. `'a' * 3` looks like be `"aaa"`, but that doesn't match the mechanism (char string) and it doesn't match...