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.

Sign up for GitHub

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

Jump to bottom

Avoid using sets when existing slices suffice #1719

Merged
merged 1 commit into from
Jul 8, 2024
Merged

Avoid using sets when existing slices suffice #1719

merged 1 commit into from
Jul 8, 2024
+29 −28

Commits on Jun 24, 2024

  1. Avoid using sets when existing slices suffice 

    Now that Go includes slice operations such as slices.Contains, some
uses of sets are no longer useful. In particular, creating a set using
a slice just to check whether the slice contains a specific item is
more expensive than checking the slice directly.

Signed-off-by: Stephen Kitt <skitt@redhat.com>
    @skitt
    skitt committed Jun 24, 2024
    Configuration menu
    Copy the full SHA
    7cb9d39 View commit details
    Browse the repository at this point in the history