[Migrated] Bindless support clarification

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.

Commencez par examiner la suppression de bindless-mode dans l’issue #710 et la prise en charge restante du chargement des buffers via Load. Comparez le comportement demandé pour ByteAddressBuffer/RWByteAddressBuffer avec l’approche actuelle des bindings globaux. C’est terminé lorsqu’une orientation à court terme approuvée ou un plan d’implémentation pour le cas d’utilisation Traverse a été défini ; aucun fichier ni test n’est nommé ici.