James Liu

Closing in favor of #89. Will try to adopt the benchmarks you have here for that implementation.

This has moved quite a bit since 2016. As @mneumann mentioned, one can now use `fb.zeroes().next()` to get the first unset bit.

Going to second the opinion that this is ideal for an ecosystem crate solution. Not every game needs it and the implementation is relatively simple to maintain separately from the...

Can you try to narrow down which potential plugin is causing this? `DefaultPlugins` includes quite a few items that could be causing this crash.

Going to assume this controversial by default due to the commitment and potential maintenance burden this may have.

Quite a few of them are. The few that aren't usually require some kind of IO, since `std::fs` and `std::net` have zero core or alloc equivalents. Assets in particular may...

Another major blocker I'm running into: `thiserror` has zero support for no_std. We could manually implement it, or find another no_std compatible error derive crate.

The primary things that we'd be missing are, as far as I know: * `std::thread` and `std::sync`. These come up for parallelization and concurrency, but we already have ways of...

This seems to at least be partially resolved as of #4715. Are we still missing anything for this issue?

For what it's worth, I do think `!Sync` components by themselves are valuable. `SyncCell` forces mutable access which may force users into triggering change detection, even when it's really just...