Lars T. Kyllingstad

> > But that will lead to a compilation error. You can't declare a member function as pure virtual and then supply an implementation anyway. > > No compile error...

It was pointed out by @lassebje in said meeting that option 1 is the least general, since it can be implemented in terms of method 2 or 3, and that...

Ah, I guess that was a bit unclear. By "users" I meant the users of our GUI and CLI, as well as the users of other sofware that builds upon...

An alternative way to put it would be: Should each cse-core-based software project have to define its own plugin mechanism for observers and connections, or can we define a common...

Are there other examples of cases where this would be useful? It kind of sounds like we have a bug in our existing error reporting channel, and the proposal is...

See #413. It appears that I posted a bug report complaining of an instance of exactly what is proposed here. ;)

Here is my interpretation of what the message tells us: * `identifier` is a function that is being compiled by us. It could be our own function, but it could...

I completely agree with @hplatou. After looking at DCPLib I went straight into we-can-do-this-way-better mode (which is definitely not the same as NIH syndrome, no sir, thank you very much)...

Some thoughts: * The code should be split into at least two layers, let's call them "transport" and "protocol". Different transports would be TCP, UDP, etc., while the protocol layer...

Regarding the transport layer, I wrote some PoC code that could be used for this when I was working on `event_loop`, but now I can't find it. But it went...