gabby

@vojtechkral: Note that other implementations might not necessarily support this feature since JSON/YAML integration is something somewhat unique to the Haskell implementation. However, there is an open issue to standardize...

My personal preference is `0o`, mainly based on Wikipedia saying that `0o` is what most new language implementations are using: https://en.wikipedia.org/wiki/Octal#In_computers

I have a PR up for the `0o` syntax: https://github.com/dhall-lang/dhall-lang/pull/1062

@singpolyma: Just to clarify, the intention of #1062 wasn't to fix https://github.com/dhall-lang/dhall-haskell/issues/1988. The discussion beginning around here clarifies that they are disjoint issues like you note: https://github.com/dhall-lang/dhall-haskell/issues/1988#issuecomment-672352319 I only created...

@singpolyma: Actually, I forgot that there is a minor reason for having language support for octals, which is primarily for `dhall-to-yaml`, so that it can convert Dhall octal literals to...

@Nadrieril: For YAML specifically it wouldn't require any changes to the Haskell implementation's AST to keep track of octal. We already preserve the original source code for numeric literals and...

@philandstuff: Just to clarify: I assume that you mean that it would no longer an arbitrary octal number, but rather always one with 3 digits, specialized to the use case...

The recent discussion made me realize that there might be a more lightweight solution to this problem, which is to add a configure flag (e.g. `-fno-cli` or `-f-cli`) to disable...

Let's call this type of value `Bytes`. I think the main thing that would help move this forward is deciding on the syntax for `Bytes` literals.

Here are two possible alternatives that I might suggest for how to encode `Bytes` literals: * Use a syntax similar to the hexadecimal notation that we permit for `Natural` numbers,...