Skip to content
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

Consider switching from vek to glam #179

Open
LegNeato opened this issue Mar 30, 2025 · 0 comments · May be fixed by #180
Open

Consider switching from vek to glam #179

LegNeato opened this issue Mar 30, 2025 · 0 comments · May be fixed by #180

Comments

@LegNeato
Copy link
Contributor

LegNeato commented Mar 30, 2025

I can't find any backstory for using vek over another lib.

rust-gpu uses glam and rust-cuda uses vek. As far as I can see, there is no real reason for it being different. It would be nice to use the same so we don't have to do import cfg() dance when sharing code between vulkan and cuda.

cust / the host side has a feature for impl_glam, but it looks on the GPU side we just support vek in cuda std?

Note glam has this feature:

  • cuda - forces glam types to match expected [cuda alignment]

Advantages for glam:

  • popular
  • unopinionated, doesn't really define anything for you except column-major matrix order
  • one of the fastest vector libs (for CPU), the dev also runs the mathbench to compare performance against other crates
  • has no_std support via libm (which vek does too)
  • glam also has support for the rkyv serializer

(thanks to @Firestar99 for the list).

LegNeato added a commit to LegNeato/Rust-CUDA that referenced this issue Apr 1, 2025
@LegNeato LegNeato linked a pull request Apr 1, 2025 that will close this issue
LegNeato added a commit to LegNeato/Rust-CUDA that referenced this issue Apr 1, 2025
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 a pull request may close this issue.

1 participant