Carl Gay

My current thinking is, * we don't have any long-term warnings (in dylan, dood, etc) that are serious warnings * keep it simple * so just make dylan-compiler exit with...

Ended up returning non-zero exit code for serious warnings by default and providing `-allow-serious-warnings` to disable that behavior.

Also document `io:print:printing-object`, which means not having to *also* import `pprint` in order to write a `print-object` method.

I posted https://groups.google.com/g/sphinx-users/c/CcnnXV2LOoY but got no response.

The answer to my question turned out to be pretty darned simple but the intersphinx docs don't make it very clear. If we have ```python intersphinx_mappings = { 'http': ('https://opendylan.org/documentation/http/',...

See the above commit for a start, but there are some issues remaining to work out, as mentioned in that PR. Also on sphinx-users they said (if I understood correctly)...

Also also, we need to be able to test the `intersphinx_mapping` locally before publishing doc changes. There's a [mechanism for this](https://www.sphinx-doc.org/en/master/usage/extensions/intersphinx.html?highlight=intersphinx#confval-intersphinx_mapping) but I decided to leave it for a later...

Peter S. Housel @housel 22:23 It does manage to infer exactly what the type of `make()` should be, it just doesn't check the assignment Same problem if it's a non-thread...

For the record we're talking about https://github.com/dylan-lang/opendylan/blob/master/build/packages/unix/README here. I guess there's no point fixing this until the **next** release though. Note that the [release checklist](https://opendylan.org/documentation/hacker-guide/topics/making-a-release.html) does mention updating that file,...

It seems to me these days the README need not be anything more than "welcome, and installation instructions are at https://github.com/dylan-lang/opendylan/blob/v2019.1.0/README.rst". (Note the URL is pegged to the specific release.)...