Andy Arvanitis

Looks good to me so far. 1. I would vote for `--build` being the default (`--no-build` being optional). 1. I'll look into `--src` and `-o` for both of my backends...

Right. I'm open to discussing it, though.

FYI, I'm good with implementing whatever changes are needed in `psgo/pscpp` to support the spago commands

@anttih > For `purescript-strings` could we do the following? > > * In `CodePoints`, get rid of `CodePoint` and use `Char`... I'd say keeping ```Haskell newtype CodePoint = CodePoint Int...

Also, code units are encoding-specific – I don't know if you can really abstract those. So if you have separate libs for those, they should be for UTF-32, UTF-16, UTF-8,...

@anttih I really don't have an opinion about `newtype CodePoint`, I just meant that it shouldn't need to change (there might be people who want/need it, I don't actually know)....

I'd recommend we keep `Char` an opaque type too (like `String`), with it representing a unicode code point – don't assume UTF-32, it would be up to backends as to...

I think even just a quick example (on Pursuit) would be helpful, at least for now. The guide is still out there and wrong, and it currently takes some digging...

I guess one thing that we would lose is the ability to use an alternative version of some set of modules without changes to source code. I'm not sure how...

Thanks for your PRs! I haven't been keeping up with purescript (or obviously my project) for quite some time, but it is nice to see some recent activity. Are you...