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

add a utility method for sorting CID slices #5

Merged
merged 1 commit into from
Sep 24, 2018
Merged

Conversation

Stebalien
Copy link
Member

@Stebalien Stebalien commented Aug 31, 2018

blocked on the CID string refactor

fixes ipfs/go-cid#46

@Stebalien Stebalien requested a review from kevina August 31, 2018 16:23
@Stebalien Stebalien added the status/blocked Unable to be worked further until needs are met label Aug 31, 2018
Copy link
Member

@dignifiedquire dignifiedquire left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

very cool, thank you

Copy link
Contributor

@kevina kevina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@kevina
Copy link
Contributor

kevina commented Sep 22, 2018

@Stebalien merge when ready.

}

// Sort sorts a slice of CIDs
func Sort(s []cid.Cid) {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not wrap either sort.Slice or sort.SliceStable and then the Slice type isn't required?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sort.Slice uses reflection so it's not quite as fast. It may not make a difference but it's not exactly a ton of code.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

True, this may just be me having an aversion to named slice types more than anything else :)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well... when go introduces proper generics all this stuff will magically disappear. Until then, we have hand-coded monomorphization.

😞

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/blocked Unable to be worked further until needs are met
Projects
None yet
Development

Successfully merging this pull request may close these issues.

It would be nice to add Less()
4 participants