Skip to content

Conversation

@nicoonoclaste
Copy link
Collaborator

Cf #70 for the rationale. TL;DR:

  • hard to implement in a stable and predictable way;
  • initially added to implement Vector2.angle, which doesn't use it anymore;
  • was never included in a release of ppb-vector.

Cf ppb#70 for the rationale. TL;DR:
- hard to implement in a stable and predictable way;
- initially added to implement `Vector2.angle`, which doesn't use it anymore;
- was never included in a release of ppb-vector.
@nicoonoclaste
Copy link
Collaborator Author

The CI failure seems to be some mypy issue unrelated to this, that I can't reproduce locally.

@AstraLuma
Copy link
Member

re mypy, see python/mypy#6036

@AstraLuma
Copy link
Member

I'm blocking this on resolving the discussion in #70.

What algorithms depend on (or significantly benefit from) cross product, even ones not included in this library? Is the instability a deal-breaker in these cases?

Can we characterize the instability? Is it something that only appears at extremes or are there perfectly reasonable vectors that have major problems?

@AstraLuma AstraLuma merged commit 6dc774f into ppb:master Dec 10, 2018
@nicoonoclaste nicoonoclaste deleted the remove-cross branch December 10, 2018 15:38
nicoonoclaste added a commit to nicoonoclaste/ppb-vector that referenced this pull request Dec 11, 2018
nicoonoclaste added a commit to nicoonoclaste/ppb-vector that referenced this pull request Dec 11, 2018
I forgot to do that in ppb#80.
Closes ppb#86 (I cherry-picked the commit from that PR)
nicoonoclaste added a commit to nicoonoclaste/ppb-vector that referenced this pull request Dec 20, 2018
I forgot to do that in ppb#80.
Closes ppb#86 (I cherry-picked the commit from that PR)
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