Jeb Brooks
Jeb Brooks
I recently switched my parsing from going over a stream of characters produced by `str::chars()` to parsing over a stream of characters from `ariadne::Source::chars()`. This makes it a lot easier...
The documentation for `custom()` states that you shouldn't need to use it, but doesn't provide any indication about how you would if you needed it. There are a few issues...
Currently to have a rule be provided as expected it must produce a token. This means that for some important syntax you end up with extra tokens in your stream....
## What problem does this solve or what need does it fill? Some post-processing or rendering effects want to be able to read from the depth buffer of previous render...
## What problem does this solve or what need does it fill? Currently, if a custom material (`impl Material`) provides a `vertex_shader(...)` implementation which performs any transformations of the vertices...
## Bevy version Mainline Bevy git+https://github.com/bevyengine/bevy.git#66f72dd25bb9e3f3d035f2f14dcbcd25674f968c ## \[Optional\] Relevant system information * EndeavourOS * Kernel 6.5.8 * Mesa: 23.2 * AMDVLK: 2023.Q3.3 * vulkan-radeon: 23.2.1 * Rust: 1.75-nightly * Broken...
## How can Bevy's documentation be improved? Neither the documentation for [ShaderDefVal](https://docs.rs/bevy/latest/bevy/render/render_resource/enum.ShaderDefVal.html) nor for the [`shader_defs`](https://docs.rs/bevy/latest/bevy/render/prelude/struct.Shader.html#structfield.shader_defs) field on the Shader (or ComputeShaderPipelines) have any information about how the defined values...