David Bakin

> Looks good to me. Feel free to squash the "address PR comments" commit. Squash done.

BTW JSON5 _does_ allow comments. As well as easier-to-use commas. (I personally prefer JSON5 but YAML has a lot of traction in tools.)

Commenting again (*) to reconsider the last point: ``` term = tfact bop+ stmts bop- ... bop- = ] ]= ]:= ``` So `foo[a]=` is a `term` (as is `foo[a]:=`)...

Well, the issue for me as I'm going through README.md is - at this stage (and perhaps forever, don't know what you have in mind) the language definition for newcomers...

ok, will come back tomorrow. obvs I understand about "docs are what they are" but at this point this is the only thing I can contribute - if you consider...

And don't forget https://github.com/shaal/awesome-gitpod

I totally get not being able to satisfy everyone at once! And I also totally get not knowing that there was anyone really depending (psychologically!) on the old behavior since...

It's not the same case, right? That case has a factory returning different instances of a test class, the `toString()` on the class can then distinguish between instances if you...

What would you think of the following text as a replacement for line 140: > However, in the common case of `SIGHASH_DEFAULT`, encoded as _0x00_, the sighash byte is omitted,...

> @david-bakin What about just: > > > This sighash byte is optional. If omitted the resulting signatures are 64 bytes, and a `SIGHASH_DEFAULT` mode is implied. OK by me.