You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
vek's types are used in the public API. So a user of this crate needs to also depend on vek. Keeping both in sync however has been reasonably painful. Especially because dependabot is now sending me PRs all the time with new versions of vek that are incompatible with euc. It would probably make sense to either not publicly depend on vek or reexport it either entirely or enough to not have to depend on it as a user of euc.
The text was updated successfully, but these errors were encountered:
I might try to schedule myself a weekend to completely overhaul euc. There are a few API corners that I feel are a bit painful to use and I'd like better support for things like textures and perhaps geometry shaders. I'll add "remove explicit dependence on vek" to the list.
vek's types are used in the public API. So a user of this crate needs to also depend on vek. Keeping both in sync however has been reasonably painful. Especially because dependabot is now sending me PRs all the time with new versions of vek that are incompatible with euc. It would probably make sense to either not publicly depend on vek or reexport it either entirely or enough to not have to depend on it as a user of euc.
The text was updated successfully, but these errors were encountered: