Nathan Ward
Nathan Ward
[Rendered](https://github.com/NathanSWard/rfcs/blob/nward/subworld-rfc/rfcs/Subworlds.md) This is based on the discord discussion starting [here](https://discord.com/channels/691052431525675048/749335865876021248/834310334264115210). This is a proposal for a `Subworlds` concept: disjoint sets of entities & their components.
Currently `Text`/`TextInput` are defined as follows: ```rust struct Text { content: String, .. } struct TextInput { placeholder: String, .. } ``` I have come across use cases where it...
### Describe the feature It's unfortunate in the Rust ecosystem that we have multiple different async runtime w/ different APIs. However, `tokio` is by far the most popular, widely used,...
This is the first step for adding a `send_timeout_async` and `send_deadling_async`. This provides the ability to consume a `SendFut` returning its contained value if the value has not yet been...
Currently `send_timeout/deadline` are implemented via blocking. This means if I want to make an `async` variant of these two, I need to use another library such as `tokio::time::timeout` - which...
I saw that under the hash specialization of tl::optional, there was a TODO for a SFINAE guard. The guard I implemented is based off of libc++'s but unlike their implementation,...
Hi! I saw within the code that the hash specialization of tl::optional still needed sfinae protection. I recently added a pull request that addresses this problem! :)