James Leitch

@rharink are you still interested in trying to get this in? Based on my very limited usage of `wasm_bindgen` and hitting this issue, I'm hoping this can get merged (and...

> Hello, is this still a desired change? 😄 I would still find this useful 🙂 One less patch 😅

The current approach I'm attempting to use is having a Flake at the `WORKSPACE` level that defines both the `devShell` and a `bazel` set under `packages."${system}"` containing any derivations I...

I think there are 3 pieces that would need to be part of a centralized repo, the `toolchain_type`, any provider definitions that get used in the `ToolchainInfo`, and the rule...

@thesayyn this PR doesn't have actually fetching the tools yet. I wanted buy in on adding this before I put that work in. Plus I'm using this with Nix so...

@alexeagle / @thesayyn greatly scoped this down to just exporting the toolchain rules. Also happy to close this and just import them from `private` in my code if that's preferred.

I updated the overall PR description to cover the motivation, which is registering these toolchains without the binaries being provided by `aspect_bazel_lib`. If that doesn't align with the goals here,...

How about something like `allow_multiple: bool` on `winit-web::event_loop::PlatformSpecificEventLoopAttributes` which could opt out of interacting with `EVENT_LOOP_CREATED` (both setting and clearing it)?

I'm not using `run()`, I'm using `spawn_app()`. I'm still not seeing a `spawn()` type API that let's me run multiple `ApplicationHandler`s in parallel. If I'm overlooking a solution that already...

> Apologies, my suggestion is that instead of adding an escape hatch to `run()` (via `PlatformSpecificEventLoopAttributes`), we can allow `spawn_app()` to run event loops in parallel _by default_. Right now...