Add Device.arch property for convenient compute capability string access

[Copilot]

This PR adds a convenient Device.arch property that returns the compute capability as a concatenated string, eliminating the need for repetitive string concatenation code throughout the codebase.

Problem

Previously, getting the compute capability as a string required this verbose pattern everywhere:

arch="".join(f"{i}"foriindev.compute_capability)
program_options=ProgramOptions(std="c++17", arch=f"sm_{arch}")

This pattern appeared in 8 locations across 7 example files and was identified as annoying repetitive code.

Solution

Added a new arch property to the Device class:

@propertydefarch(self) ->str:
"""Return compute capability as a string (e.g., '75' for CC 7.5)."""return"".join(f"{i}"foriinself.compute_capability)

Now the usage is much cleaner:

arch=dev.archprogram_options=ProgramOptions(std="c++17", arch=f"sm_{arch}")

Changes

• Added Device.arch property in cuda_core/cuda/core/experimental/_device.py
• Updated 8 occurrences across 7 example files to use the new property:
  • cuda_core/examples/vector_add.py
  • cuda_core/examples/simple_multi_gpu_example.py (2 occurrences)
  • cuda_core/examples/pytorch_example.py
  • cuda_core/examples/strided_memory_view_gpu.py
  • cuda_core/examples/saxpy.py
  • cuda_core/examples/cuda_graphs.py
  • cuda_core/examples/memory_ops.py
• Added comprehensive test for the new property in test_device.py
• Preserved existing test files unchanged as requested

Benefits

• More concise and readable code
• Eliminates repetitive string concatenation
• Provides a clear, discoverable API
• Maintains full backward compatibility
• Works correctly with all compute capability values (tested with edge cases)

Fixes#729.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[leofang]

@copilot looking good! One nit: in all samples, could you just merge the dev.arch access to the f-strings where arch is needed, instead of having a separate call?

[Copilot]

@copilot looking good! One nit: in all samples, could you just merge the dev.arch access to the f-strings where arch is needed, instead of having a separate call?

Done! I've updated all the example files to inline the dev.arch calls directly into the f-strings instead of having separate variable assignments. This makes the code more concise as requested. Changes made in commit c940eca.

[leofang]

@copilot looking good, please add a release note

[Copilot]

@copilot looking good, please add a release note

Added release note for the new Device.arch property in the "New features" section. The note documents the property and its convenience benefit. (7fc9d1b)

[leofang]

/ok to test 7fc9d1b

[kkraus14]

/ok to test

[copy-pr-bot]

/ok to test

@kkraus14, there was an error processing your request: E1

See the following link for more information: https://docs.gha-runners.nvidia.com/cpr/e/1/

[kkraus14]

/ok to test 491fb89

[github-actions]

Doc Preview CI
Preview removed because the pull request was closed or merged.