nordic-dev.net/rust-gpu
2
0
Fork 0
mirror of https://github.com/EmbarkStudios/rust-gpu.git synced 2024-11-21 22:34:34 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update 001-resource-binding-syntax.md (#236)

Browse Source 
small typo
This commit is contained in:
Dhruv Dhamani 2020-11-13 02:38:26 -05:00 committed by GitHub
parent e8aef14347
commit e261b88a73
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/src/rfcs/001-resource-binding-syntax.md
View File

@ -163,7 +163,7 @@ fn main(inputs: &ShadingInputs, indirect_lighting: &IndirectLighting) {
# Suggestion # Suggestion
I think the most ergonomic and future proof binding method would be to have descriptors in structs, bound to the entrypoint. This allows us some nice, even more ergonomic upsides later on (when support is more widely available) where we can put data members in these structs as well. And along wit this, we can have very egonomic CPU side code as well, where we can keep shader invocation looking like a function call for a large part, instead of having to manually bind to slots again. I think the most ergonomic and future proof binding method would be to have descriptors in structs, bound to the entrypoint. This allows us some nice, even more ergonomic upsides later on (when support is more widely available) where we can put data members in these structs as well. And along with this, we can have very egonomic CPU side code as well, where we can keep shader invocation looking like a function call for a large part, instead of having to manually bind to slots again.
# Prior art # Prior art
@ -238,4 +238,4 @@ RLSL also passes resource bindings as arguments to the kernel, with two template
#[spirv(compute)] #[spirv(compute)]
fn compute(compute: Compute, buffer: Buffer<N0, N0, RuntimeArray<f32>>) fn compute(compute: Compute, buffer: Buffer<N0, N0, RuntimeArray<f32>>)
``` ```
</details> </details>