Philip Potter

I had a brief look at using node's `readline` module to fix this, but that seems to do way more than just the line-buffering that is desirable here.

I agree with @singpolyma: I'd prefer to keep the language small by default, and only add new features where there is a strong motivating use case. I'd also add that...

As a note, it would be pretty painless to add octal literals because they are currently a syntax error: #898

If we were designing in a vacuum without the baggage of history behind us, I’d agree that `0o` is a better prefix. But there is a long tradition of using...

It seems as if octal numerals have precisely one use case: file permissions. Maybe it’s worth reframing / renaming this issue to be around support for that specific use case....

No, I’m just saying that although the headline issue is about octal numbers, the thing that people actually care about is file permissions. Octal numbers are one solution to the...

I have previously written a similar utility which takes an `Optional x` and provides a JSON map entry in a list of length one if present, or an empty list...

I would like this, and I don’t see it as hard to implement. The main hazard I can see with standardisation / implementation is getting scoping right for the result...

Given this issue is about the *semantics*, I think having a hand-rolled parser that attempts to match the abnf is perfectly fine for now. This would allow us to break...

We already special case union types to allow selecting constructors from them; it feels natural to do the same for JSON. ``` let Color = < Red | Green |...