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

Sort by value spike #218

Closed
wants to merge 54 commits into from
Closed

Sort by value spike #218

wants to merge 54 commits into from

Conversation

scanny
Copy link
Contributor

@scanny scanny commented Sep 2, 2020

Still very much WIP at this point, but it works and it's probably good for folks to be able to take a look at how it's shaping up.

@coveralls
Copy link

coveralls commented Sep 2, 2020

Coverage Status

Coverage decreased (-0.4%) to 99.578% when pulling ebe0f2c on sort-by-value-spike into 9745bb1 on master.

@scanny scanny force-pushed the sort-by-value-spike branch 6 times, most recently from 04e382f to c1895aa Compare November 9, 2020 23:12
Remove unearned abstraction of separate `._iter_cubes()` method. Inline
it in the only caller.
Classic example of YAGNI from a couple years back.
The "Matrix" specifier is redundant, this class is local to the `matrix`
module and so can only apply here. I think this naming came from early
on when we though that a stripe would just be an unopposed slice-vector,
but that of course turned out not to be the case.
Also fix redundant definition for ._anchors which is going away anyway.
OPPOSING_ELEMENT doesn't handle HS yet, need to add some tests for that.
@scanny scanny closed this Nov 19, 2020
@scanny scanny deleted the sort-by-value-spike branch November 19, 2020 06:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants