Blaine Bublitz

Here's a rough outline: 1. ~~Manually regenerate the docs on the release PR.~~ Auto generated as of #1777 1. Release PR is merged with a better message than the default....

Additional work that was found: 12. ~~Run graindoc on stdlib with an updated version https://github.com/grain-lang/grain-lang.org/pull/289~~ 13. ~~Update website docs with the stdlib graindoc sync. #934~~

Ideally, we'd also want to test our CI release process before trying to roll it out so we don't have the failing CI issue.

~~Until #1408 is completed, we'll want to manually regenerate the docs on the release PR before releasing.~~

I'm 100% against using string types for file paths. They have caused so many miserable bugs in the compiler.

You probably want to go look at ReasonNative's Fp library. They encode file paths interestingly.

@mindplay-dk there will never be a "js backend", just as there will never be an x86 backend. Those are not the goal of the language and you'd be better off...

I assume this and #989 go hand-in-hand?

It also disallows `(|||)`

I think we should do something about allowing any combination of those characters in bindings. Even if it's only between parens. It's really weird/unexpected behavior that I can define bindings...