Skip to content

Conversation

@197g
Copy link
Member

@197g 197g commented May 24, 2025

No description provided.

197g added 2 commits May 17, 2025 16:01
This changes the internal macro defining the inherently available
`Texel` implementations. The macro calls now take an additional unsafe
keyword and comment to justify that usage. When provided the call allows
arbitrary types but otherwise requires the type to be `bytemuck::Pod` at
const time. This works around having to surface all kinds of different
features covering parts of bytemuck's SIMD implementations.

I expect that some of this will become less intricate if
`#[cfg(rust-version())]` (or w/e it is spelled) will be supported since
this would get rid of the need for such feature flags in bytemuck. Iff
they bump to `2` as to only support compiler versions that support such
a configuration macro. Which.. yeah. Anyways we can at least add
implementations for new SIMD types as they are stabilized.
@197g 197g merged commit 62068a8 into master May 24, 2025
8 checks passed
@197g 197g deleted the texel-ref-new branch May 24, 2025 17:02
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