Bill Avery

I'm not sure if I understand the question, it's been a while since I played with `Boost.asio`, and I wasn't using C++ coroutines yet at the time. Can you point...

I took a look at your sample, and I think this may require a change in `cppgraphqlgen`, specifically for the awaitable types. The `await_suspend` call only takes a `coroutine_handle`, whereas...

I tried some tweaks to `AwaitableScalar::await_suspend`, but I wasn't able to get it to work with the `boost::asio::awaitable` `promise_type` (or vice versa). I think the lack of executors in the...

I think maybe I could implement something like this on `AwaitableScalar::promise_type` as: ```c++ template AwaitableScalar await_transform(U awaitable) { // ... } ``` That should implicitly convert `co_await` for `boost::asio::awaitable` to...

Would it make more sense to expand to `extern "system"`? The [note](https://doc.rust-lang.org/nomicon/ffi.html#foreign-calling-conventions) in the nomicon seems to indicate that it would pick the appropriate `"stdcall"` default for `i686-pc-windows-msvc`, and use...

It's not as simple as switching to `extern "system"`. Unless I set `CXXFLAGS="/Gz"` in the environment, building `i686-pc-windows-msvc` fails because apparently MSVC doesn't set the default calling convention to `__stdcall`....

Ah, I found where it's getting the `@0` for the argument size: ```rust #[link_name = #c_trampoline] fn trampoline(); ``` The compiler is able to figure out that it should be...

I wanted to build one of my apps for an ARM64 Surface and did a little digging. It looks like the wix4 toolset is where the active development is happening....

BTW, while it does fail to build the install package, I found the executable in /src-tauri/target/aarch64-pc-windows-msvc/release and it worked fine when I copied it manually to the ARM64 device.

> Couldn't it all be chained to a single top-level `std::shared_ptr` so they all share the operation's lifetime? Come to think of it, you might even be able to use...