Skip to content

Conversation

jeapostrophe
Copy link

This PR exposes a few more raw handles that I found necessary to integrate an existing C library with my Rust WGPU program through exposing the underlying Ash objects.

@cwfitzgerald cwfitzgerald self-assigned this Sep 3, 2025
Copy link
Member

@cwfitzgerald cwfitzgerald left a comment

Choose a reason for hiding this comment

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

Some CI issues and a nit

}

impl PhysicalDeviceFeatures {
pub fn get_core(&self) -> vk::PhysicalDeviceFeatures {
Copy link
Member

Choose a reason for hiding this comment

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

This probably needs a better name, but this isn't a blocker.

Copy link
Author

Choose a reason for hiding this comment

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

Yes. I don't like the name. All of the functions like this in the codebase don't have a consistent naming scheming... the closest is that many of them are get_X where X is the field. I think it would be more beautiful to have it also be raw or handle or something like that, but I tried to be consistent in this (simple) PR

Copy link
Member

Choose a reason for hiding this comment

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

Fair enoguh

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