Mathew Polzin

Not sure if it’s really worth much to support Heroku out of box but that would come for free with the ENV var named PORT

We could establish a precedent (much like that of “put a file in your repository named LICENSE.txt”) of committing the JSON output of `swift test --enable-code-coverage` to the repository with...

> longer-term ambition to actually build and test packages automatically That’s ambitious! Would be very cool.

Building on the idea that packages will be built by the indexer, it would be relatively easy to get the code coverage percentage (whether to display correctly, or even just...

I can try that if you'd like to know if it works for me, but I don't think it will help me work around the problem in my case. I...

It’s not pack I don’t think. My nightly CI for pg-idris started failing as well: https://github.com/mattpolzin/pg-idris/runs/6785534578?check_suite_focus=true

I think (2) describes roughly what the FFI documentation (undoubtedly written mostly or entirely with the Scheme backend in mind) describes currently, if I am understanding correctly. Snippet from the...

If you can `%runElab $ print …` then can’t you make `print` (or whatever you want to name the function) into a macro and get exactly the syntax `%print …`?...

RE naming the new functions: no strong preference from me, but if you use the word “truncate” somewhere in the documentation (if not the function name) then I think it...

You've gone a different direction with your test file -- making a single file and name spacing it by folder in a way that reminds me of unit tests instead...