Carl Gay

Having another warning (or note, like clang does) as mentioned above would help a lot, but I think the initial warning should be a lot more explicit about what types...

Standard vector DFM... ``` METHOD quicksort! (a :: , lo, hi) => (#rest results) {{ lo }} := make-cell({{ lo }}) @??? | {{ lo }} :: \ {{ lo...

Sorry, I missed this issue when it was created. I agree, and it's on my list. Assigning to myself.

The original comment is a bit vague, but I think the "sprinkled around" part of this has been addressed. I've also changed testworks such that test "apps" are no longer...

We're getting closer to this. Currently working on making the existing test suites pass by fixing the simple issues, then by marking long-standing, difficult issues as expected to fail. Then...

Status: * I'm considering the "sprinkled around" problem to be solved enough that remaining problems can be addressed one-by-one. * I've made a start at GitHub CI with GitHub Action...

The CI depends on #1373, and fixing #1373 will cause the `libraries-test-suite` build to fail due to tests like this: ``` .../opendylan/sources/common-dylan/tests/common-extensions-tests.dylan:154.37-54: Serious warning - Reference to undefined binding {this-is-undefined...

Maybe `direction: #"output", if-does-not-exist: #f` is unlikely to be used (only write to the file if it already exists?) but presumably it should do the same as for `#"input"`: just...

Added Usability label. Defining a new library and module is one of the first things you do as a new user, so compiler warnings are particularly important. (Somewhat mitigated by...

Explicitly importing a non-existent name from a module doesn't get reported on the console, nor is it in the log file. e.g., `use format-out, import: { format-out, my-dog-has-fleas };`