Donal Fellows

As a ***workaround***, just force the version of `coverage` to be at least 4.4 by pip-installing that over the top; that seems to work with our tests. (OK, they're not...

In file `interface.h`: ```c //! This struct has multiple definitions, depending on build options typedef struct foo foo; ``` In file `implementation-1.c` ```c //! \file #include "interface.h" //! \brief Implementation...

The most obvious possible source of problems is failing to close resources (connections, statements, result sets) or keeping transactions open. (Also make sure that transaction start has a timeout and...

I don't mind having to generate this on a per-file basis when wanting to override the defaults. Fiddly, but quite doable.

Even the name-coupled branch builds are failing. What's going on?

State of things: they do what they do competently. Whether they do what they should do… 🤷

I would love to have the C in a separate repo anyway, both for sPyNNaker and FEC. The current approach is a bit too "mulch together" for my taste. Low...

While producing a JSON description of the PyNN-level graph might _also_ be a good idea, this report has its own value.

Sounds like the `__bitfields` generator isn't synched with the data structures on the chip.

But _do we need these reports at all?_