Rust-GPU / Rust-GPU/rust-gpu

[Migrated] Bindless support clarification

Open
#124 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
3.4k
Forks
125
PR merge metrics
No merged PRs in 30d

Description

Issue automatically imported from old repo: https://github.com/EmbarkStudios/rust-gpu/issues/733
Old labels: t: bug
Originally creatd by Jasper-Bekkers on 2021-08-20T22:42:07Z 👀: 1


Now that the full bindless mode has been stripped (#710), I would like to open up this issue so that we can all get on the same page and see if we can support the Traverse use case as well. I'd like to inquire about near-term steps forward when it comes to bindless.

  • What are the plans for the equivalent of bindless ByteAddressBuffers going forward?
  • What is the current trajectory for specifying bindings as globals in rust-gpu?

In the remove code there was a bunch of stuff supporting the equivalent of ByteAddressBuffer/RWByteAddressBuffer (meaning, no the buffer type gets decided in Load and multiple datastructures can be loaded from the same buffer at same / different offsets).

If there are no plans for this near term, could we look at reverting the code-removal while we get a plan together? Currently we'll have to straddle behind releases or fork the project which is really unfortunate.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the bindless-mode removal in issue #710 and the remaining support for buffer loading through Load. Compare the requested ByteAddressBuffer/RWByteAddressBuffer behavior with the current approach to global bindings. Done means an agreed near-term direction or implementation plan for the Traverse use case; no file or test is named here.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers, computer-graphics
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.