Kip

@Lectem, can you please let @Tachi107 and I know if his recently merged PR addresses your concerns?

@Tachi107, something else to keep in mind is that if the new build flags also require changes in flags used by a user who is linking against the library, those...

Sorry, do you mean flags necessary to build the library, or those necessary to link against the binary?

@dennisjenkins75, one thing we could do is add some kind of user provided "allocator" class, like the STL containers, but for threads. The default allocator has a fixed pool or...

Thanks @Majestro000. Although I cannot read German, I'll try to use a translator. Hopefully we see more positive articles on our work. Maybe we should start archiving links to the...

Sorry, but what is a dilatation?

Hey @Tachi107. Thanks for your work. Regarding your notes, "_Lastly, this autopkgtest CI is a bit redundant, as the Launchpad PPA does the same exact thing more reliably and on...

We could do that, but then we lose the benefits of testing on other architectures which, historically, have been quite fruitful for us in finding weird bugs with memory alignment,...

> We wouldn't, as Launchpad runs normal tests on multiple architectures. Running autopkgtest on multiple archs specifically doesn't help _that_ much, the only thing that's tested is compilation. Not just...

> All these steps will still be executed, but only on amd64. > > * dependency calculation: is handled by apt, not us, and dependencies do not change between architectures...