Yotam Gingold

Thanks for the swift reply. I'll ask my followup question as a separately.

C++14 went with quote marks: 400'000'000. They considered spaces: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3499.html#Typographic C++ rejected spaces because: * It does not match the syntax for a pp-number, and would minimally require extending that...

@pressureless What parsing issues would arise if we were to support an optional comma, period, or space ("," or ".", or " ") between digits for numerical literals?

And period would cause ambiguity with decimal place: `123.456`. That leaves spaces. What issues arise there? `123 456`? Multiplication, though I think this is a case where you would write...

That `[123 456]` is a `1×2` matrix whereas `123 456` is a scalar equal to 123456 doesn't bother me, since users are familiar with spacing inside matrices being interpreted differently...

These are terrifying examples. I think there must be numbers surrounding a period without spaces. `12. 34` should be illegal for that reason. I know that some programming languages allow...

Every three digits to the left of the decimal place sounds reasonable to me. I checked other languages with digit separators (Python, Julia, C++14) and they support the digit separator...

I am leery of treating subscripts differently depending on whether a sequence is present or not. That seems like it would lead to a lot of user confusion. I am...

I like this. This is a clean idea. Are there any issues with how this would be implemented in the backends? I don't foresee any. This only applies to sequences....

Thank you for taking the time to do this. ## Paths Your change is good and added. I thought `/usr/bin/env` was necessary for `subprocess.run` to use the environment variables, but...