-
Notifications
You must be signed in to change notification settings - Fork 8
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
Use new vector type in existing code #85
Conversation
a835ed8
to
9a77b48
Compare
aefeac5
to
73c8469
Compare
This PR is failing tests so it has been put back into draft. Please remove the draft status when the tests pass. |
73c8469
to
cd87c3e
Compare
9a77b48
to
ffed00c
Compare
cd87c3e
to
cde9698
Compare
It seems that this implementation may be slower than the use of Coordinate/TaggedVector. Maybe bad luck on persee, maybe related to the comments on previous PRs |
61db95a
to
29005c6
Compare
1adbe02
to
95f84b0
Compare
29005c6
to
18b63f9
Compare
95f84b0
to
5137c5a
Compare
6679fa4
to
03f6fb5
Compare
This PR is failing tests so it has been put back into draft. Please remove the draft status when the tests pass. |
This PR is failing tests so it has been put back into draft. Please remove the draft status when the tests pass. |
It seems like you haven't finished working on this PR so it has been put back into draft. Please remove the draft status when the PR can run tests without being interrupted. |
Use the new vector type that arises from #81 in the existing code.
This PR must be merged after #81