Refactor for wgpu v23 compatibility with an example of wgpu device sharing

[AsherJingkongChen]

Related Issues/PRs

• Refactor for wgpu v23 compatibility burn#2435
• Remove IDs from wgpu traits gfx-rs/wgpu#6134
• v23.0.0 release gfx-rs/wgpu#6465

Checklist

• Confirmed that cargo xtask test --ci script has been executed.
• Made sure the book is up to date with changes in this PR.
• Checked for any updates or changes in dependencies.

Changes

1. Modified entry_point Type

• Change: Updated the type of entry_point from &str to Option<&str>.
• Reason: Clippy's suggestion

2. Updated WgpuDevice::Existing Enum Type

• Change: Altered the type of WgpuDevice::Existing from wgpu::Id<wgpu::Device> to u32.
• Reason: After the changes introduced in gfx-rs/wgpu#6134, wgpu::Id no longer exists. Using a u32 ensures a unique identifier for WgpuDevice::Existing.

Note: We avoid using pointers as identifiers due to the possibility of reallocation at the same memory address. To maintain uniqueness, a monotonically increasing value is now used internally.

Examples

1. Added device_sharing Example
   • Description: This example demonstrates the device sharing feature.
   • How to Run: Use the following command to run the example:

     cargo run --example device_sharing --features wgpu

[ArthurBrussee]

In theory now that the OOB behaviour has been fixed this should work now, if you have time to re test on metal would be amazing :) Thank you!

[nathanielsimard]

In linux CI, there is a segfault without message, would it come from CUDA? I can't resolve it now.

I don't think the CI is building CUDA.

[nathanielsimard]

@AsherJingkongChen If you merge main, does it fix the CI?

[AsherJingkongChen]

I don't get it why did it pass CI. I just updated feature flags. LOL.

[syl20bnr]

I don't get it why did it pass CI. I just updated feature flags. LOL.

This is because the CI errors was caused by the spirv feature which is not yet fully functional on CPU.