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

Lost features #501

Closed
InnocentusLime opened this issue May 15, 2020 · 2 comments
Closed

Lost features #501

InnocentusLime opened this issue May 15, 2020 · 2 comments
Labels

Comments

@InnocentusLime
Copy link

InnocentusLime commented May 15, 2020

There are some fancy methods implemented for Decomposed<V : VectorSpace, R>, when V : EuclideanSpace. However that trait bound introduces a problem:
There is no type T which satisfies both EuclideanSpace and VectorSpace (EuclideanSpace is only implemented for Points, but they do not implement VectorSpace). As a result Decomposed<V : VectorSpace, R> where V : EuclideanSpace is an uninhabited type.

@nstoddard
Copy link
Contributor

Can you give a specific example of a method that isn't callable for any type? I don't see any methods that require both EuclideanSpace and VectorSpace, but maybe I missed some. The closest I can find is an impl that requires P: EuclideanSpace and P::Diff: VectorSpace, but Point3 etc would satisfy that (since Point3::Diff would be Vector3).

@InnocentusLime
Copy link
Author

Okay, you are right. I got lost in the trait bounds. xD

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants