Skip to content

Conversation

cwfitzgerald
Copy link
Member

This changes our api a bit to force people to explicitly enable experimental features with an unsafe api before they can enable them, helping to clear up that these are not yet fully sound.

@cwfitzgerald cwfitzgerald requested review from crowlKats and a team as code owners August 28, 2025 00:06
@cwfitzgerald cwfitzgerald requested a review from kpreid August 28, 2025 00:06
@cwfitzgerald cwfitzgerald requested a review from kpreid August 28, 2025 19:11
@cwfitzgerald cwfitzgerald force-pushed the cw/experimental-features branch from 3250508 to c02ac2d Compare August 28, 2025 21:55
@cwfitzgerald cwfitzgerald force-pushed the cw/experimental-features branch from c02ac2d to 3ef31fc Compare August 29, 2025 04:17
@cwfitzgerald
Copy link
Member Author

cc @SupaMaggie70Incorporated @Vecvec

@Vecvec
Copy link
Collaborator

Vecvec commented Aug 29, 2025

I think this is a great idea!

@SupaMaggie70Incorporated
Copy link
Contributor

I think this is a great idea!

I second this, I think its a good way to communicate that these technically not unsafe functions aren't battletested/guaranteed to work perfectly.

@ErichDonGubler ErichDonGubler merged commit 8d1f4bb into gfx-rs:trunk Aug 29, 2025
40 checks passed
@cwfitzgerald cwfitzgerald deleted the cw/experimental-features branch August 29, 2025 21:42
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.

7 participants