Skip to content

docs(vulkan): clarify safety contract for DeviceShared::set_object_name #8055

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: trunk
Choose a base branch
from

Conversation

ErichDonGubler
Copy link
Member

Motivated by discussion in #8043.

@ErichDonGubler ErichDonGubler requested a review from a team as a code owner August 6, 2025 13:43
@@ -27,7 +27,17 @@ impl super::DeviceShared {
///
/// # Safety
///
/// It must be valid to set `object`'s debug name
/// This method inherits the safety contract from [`vkSetDebugUtilsObjectName`]. In particular:
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question: I think this might be stricter of a requirement than actually necessary. I suspect the only requirement here is that the object in question hasn't been destroyed in the Vulkan runtime yet.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just tried summarizing the relevant parts of the Vulkan spec. with 2e1f81d, rather than a hot-take must-be-safe approach that doesn't necessarily mesh with Vulkan terminology.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants