Joel Bodenmann

As discussed previously: I am all pro using coroutines - but unfortunately not unless MinGW-w64 & GCC shipped by MSYS2 can compile `malloy`.

I wanted to add this mental note ever since I read the changelog of boost v1.77.0: There are changes to coroutines. Might be worth exploring. Personally I would be okay...

Awesome to hear from you again! :) I really don't know what to tell you... this is a difficult situation... Overall I do think that going for proper coroutines is...

> Personally I think I'm going to at least try converting one or two paths of the websocket interface, and see how messy/possible it is (unless you have any major...

Nice work! I can have a much closer look at this on the 2nd of January. Unfortunately I could only glance over your work so far. Compile times are a...

> Yes. It will allow supporting all current environments + using the cool new stuff as and when it becomes available with no extra code changes from us. I see...

Hi, Could you provide a bit more information on the scenario/setup that leads to these errors in 99% of the time? What operating system is malloy running on, which compiler...

Can you reproduce the same behavior by running one of the examples that ship with malloy such as `malloy-example-server-basic`? When you run such an out-of-the-box example, do you observe the...

You're right - `SOCI_VISIBILITY ON` makes no sense with `SOCI_SHARED OFF`. I rectified that. But as expected that didn't have any effect on the problem I'm facing. Yes, it happens...

I tried consuming SOCI as a shared library but same problem: It fails to link `libsoci_core.dll`: ``` [1/8] Linking CXX shared library bin\libsoci_core_4_1.dll FAILED: bin/libsoci_core_4_1.dll lib/libsoci_core_4_1.dll.a C:\Windows\system32\cmd.exe /C "cd ....