Lars T. Kyllingstad

The example above was just off the top of my head, there are probably several issues with it. The point was to give a feel for what I had in...

As mentioned in the meeting, I think we should strive to use `cse::async_slave` as the interface to slaves regardless of protocol.

Regarding the serialisation/deserialisation mechanism: There are a bunch of different message (aka. PDU) types in DCP, and depending on how many of them we actually need in "our" DCP subset,...

I couldn't help myself, and even started (over)thinking of how to handle endianness and similar encoding issues. ;) ```.cpp template class serialized_integer { public: serialized_integer& operator=(T value) { // Encode...

Pull request #777 dynamically prevents adding/removing subsimulators after initialisation, so it is a step in the right direction. But I think it would be even better to prevent it statically,...

Hm. Seems like my little trick of storing an incomplete `node` type in an `unordered_map` doesn't work on GCC 9. It worked locally for me, but I use a more...

Ok, I made it work now. It seems that to make a recursive map-like data type in standard C++, one has to hide the internal type, for example by messing...

An `execution` represents one co-simulation run, so maybe just rename it to `cosim::run`?

The `simulator`/`slave` thing is tricky. They represent the same entity, but on different levels and for different users: * `slave` is the lowest-level one, and it abstracts away the interface...

For `model`, I think my preference would be to follow the newer convention established by `function` and `function_type`. So whatever `slave` ends up being called, `model` would be renamed to...