Skip to content

Keep ifs with else: nil (explicit is better) and format the library #9

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
Merged
remotecom merged 2 commits into from
Jun 7, 2025
Merged

Keep ifs with else: nil (explicit is better) and format the library #9

remotecom merged 2 commits into from
Jun 7, 2025

Conversation

@remotecom
Copy link

@remotecom remotecom commented Jun 7, 2025

  • Keep ifs with else nil statements for explicitness.
  • Formats the library.
  • Removes a missed merge conflict line.

@remotecom remotecom changed the title Keep if-s with else nil (explicit is better) and format the library Keep ifs with else: nil (explicit is better) and format the library Jun 7, 2025
@remotecom remotecom merged commit 463bcb5 into main Jun 7, 2025
10 checks passed
@remotecom remotecom deleted the keep-else-nil branch June 7, 2025 00:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@remotecom @JesseHerrick