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

feat: nil version equality #213

Merged
merged 1 commit into from May 14, 2024

Conversation

KnutZuidema
Copy link
Contributor

This changes the Equal method to return true for 2 nil values and false if any one of the values is nil. Previously passing a nil value would have resulted in a panic.

This changes the Equal method to return true for 2 nil values and false if any one of the values is nil. Previously passing a nil value would have resulted in a panic.
@adamperlin
Copy link

Just adding another comment in favor of this PR! I just ran into a panic when calling equal on a nil version. It would be great if this case was handled!

Copy link
Member

@mattfarina mattfarina left a comment

Choose a reason for hiding this comment

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

This flow makes sense. It's a minor optimization for some cases and it stops a panic from happening in some other places.

Note:

a := MustParse("1.2.3")
b := MustParse("1.2.3")

// a != b

To get equality with == you need...

a := MustParse("1.2.3")
b := a

// a == b

@mattfarina mattfarina merged commit 347f541 into Masterminds:master May 14, 2024
@KnutZuidema KnutZuidema deleted the feat/nil_equal branch May 15, 2024 13:39
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.

None yet

3 participants