Ray Queries

[Vecvec]

Connections
Works towards #1040

Description
This PR provides BLASes (bottom level acceleration structures), TLASes (top level acceleration structures), TLAS instances (which contain BLASes and data, like transforms, about them), TLAS packages (which contain vectors of TLAS instances).

Testing
Running tests & examples included in PR

This a updated version of #3631 and is intended to replace it.

Checklist

• Run cargo fmt.
• Run cargo clippy. If applicable, add:
  • n/a --target wasm32-unknown-unknown
  • n/a --target wasm32-unknown-emscripten
• Run cargo xtask test to run tests.
• Add change to CHANGELOG.md. See simple instructions inside file.
• More tests & examples.
• More docs

Later (follow-up PR)

• Acceleration structure compaction.
• Procedural geometry.
• as_hal methods

[Vecvec]

The validation should be refactored away from storing mutable state on the TLAS/BLAS itself and move to a tracker-like way of validating state.

@cwfitzgerald what would this be like (would there be a FastHashMap<TrackerIndex, Option<NonZeroU64>>?)

[Vecvec]

I have noticed that quite a few resources use snatchables and it seems that they are used in resource destruction if the resource is in something such as a bind group, I will implement snatch guards for BLASes and TLASes while @cwfitzgerald works on moving the validation away from a mutable state on the BLAS/TLAS.

[Vecvec]

@cwfitzgerald you were working on moving the validation away from a mutable state on the BLAS/TLAS, do you know how long that might take? It seems that other people are working off this branch (for example: #1040 (comment)), so it would be useful to get this branch into trunk.

[JMS55]

I coincidentally had just asked @cwfitzgerald about this on matrix. Posted their response below, with the first part paraphrased.

[explaining that they don't have time to work on this anymore]. However we don't actually want to block it at this stage so our resolution to this problem is to let it in basically as is. The one change that we want to make is prefix the feature flag with EXPERIMENTAL_ so that people will expect it to not work sometimes or break or break your computer [or] whatever.

So sounds like we can merge once you rename the feature flag :)

[cwfitzgerald]

Good after failing CI fixed

[JMS55]

Thanks so much @Vecvec! What a great birthday present ❤️