Disclaimer: I work on Vello[0], but not on the Skia integration directly My understanding, having not dug into it too much, is that the Skia integration does exist, but isn't enabled by default/any clients at the…
WGSL (the shading language for WebGPU) has something similar[1]. For example, `a + b << c` will fail to parse in a conforming implementation, as will `a << b << c` and `a && b || c`. Note however that `a && b && c` does…
> From a Rust-on-WASM perspective, it might be useful to limit the entity id's to ~52 bits or less, since native JavaScript numbers are doubles. Since compiling to web uses WebAssembly, we can just use native 64 bit…
In unfamiliar UIs, I often find myself accidentally triggering keyboard shortcuts and getting into weird states, so 1) leading to 2). A classic example is changing into override mode[0] in Microsoft Word or similar[1].…
Are you familiar with `core::other::from_fn`[1]. This allows converting from `impl FnMut() -> Option<T>` to `impl Iterator<Item = T>`. I recognise that these aren't strictly generators - you need to do your own state…
To copy from another comment[0] elsewhere in the thread from cart: > The story is similar for networking. Ultimately we will have a built in api, but we're focused on more fundamental things at the moment. There are…
Yes, indeed. This was mentioned in 0.6's release notes[0]. However, this is the first actual stop of the train, so we probably could have mentioned it in these release notes as well. [0]:…
A change I find interesting in this release is the addition of `Deref`/`DerefMut` derives[0]. It addresses a very real pain point in bevy, due to `#[derive(Component)]`'s interaction with the orphan rules requiring…
I don't think this is actually a problem, since when casting from `&mut T` to `*mut T`, the returned pointer can only access the data (the T value) directly behind the reference. The raw pointer would be synthesised…
One potential option I haven't seen mentioned is to make references (i.e. `&[mut] T`) not use capabilities, but raw pointers (`*(mut|const)`) to use capabilities. Since the compiler already guarantees that references…
I can't speak for cart here, but from my perspective as a contributor to `bevy`, it's extremely useful having freedom from backwards compatibility concerns to improve our APIs. For example, we want to rework our input…
You can either use rust-analyzer[1] (for which vscode is most well supported), or IntelliJ Rust [2]. Personally, I use `rust-analyzer` with vscode as a bevy developer. [1]: https://github.com/rust-analyzer/rust-analyzer…
Disclaimer: I work on Vello[0], but not on the Skia integration directly My understanding, having not dug into it too much, is that the Skia integration does exist, but isn't enabled by default/any clients at the…
WGSL (the shading language for WebGPU) has something similar[1]. For example, `a + b << c` will fail to parse in a conforming implementation, as will `a << b << c` and `a && b || c`. Note however that `a && b && c` does…
> From a Rust-on-WASM perspective, it might be useful to limit the entity id's to ~52 bits or less, since native JavaScript numbers are doubles. Since compiling to web uses WebAssembly, we can just use native 64 bit…
In unfamiliar UIs, I often find myself accidentally triggering keyboard shortcuts and getting into weird states, so 1) leading to 2). A classic example is changing into override mode[0] in Microsoft Word or similar[1].…
Are you familiar with `core::other::from_fn`[1]. This allows converting from `impl FnMut() -> Option<T>` to `impl Iterator<Item = T>`. I recognise that these aren't strictly generators - you need to do your own state…
To copy from another comment[0] elsewhere in the thread from cart: > The story is similar for networking. Ultimately we will have a built in api, but we're focused on more fundamental things at the moment. There are…
Yes, indeed. This was mentioned in 0.6's release notes[0]. However, this is the first actual stop of the train, so we probably could have mentioned it in these release notes as well. [0]:…
A change I find interesting in this release is the addition of `Deref`/`DerefMut` derives[0]. It addresses a very real pain point in bevy, due to `#[derive(Component)]`'s interaction with the orphan rules requiring…
I don't think this is actually a problem, since when casting from `&mut T` to `*mut T`, the returned pointer can only access the data (the T value) directly behind the reference. The raw pointer would be synthesised…
One potential option I haven't seen mentioned is to make references (i.e. `&[mut] T`) not use capabilities, but raw pointers (`*(mut|const)`) to use capabilities. Since the compiler already guarantees that references…
I can't speak for cart here, but from my perspective as a contributor to `bevy`, it's extremely useful having freedom from backwards compatibility concerns to improve our APIs. For example, we want to rework our input…
You can either use rust-analyzer[1] (for which vscode is most well supported), or IntelliJ Rust [2]. Personally, I use `rust-analyzer` with vscode as a bevy developer. [1]: https://github.com/rust-analyzer/rust-analyzer…