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

Rename function to reverseRange #678

Merged
merged 1 commit into from
Jan 4, 2025
Merged

Rename function to reverseRange #678

merged 1 commit into from
Jan 4, 2025

Conversation

noborus
Copy link
Owner

@noborus noborus commented Jan 4, 2025

The function was renamed to reverseRange as it better describes its purpose compared to the previous name reverseLine.

The function was renamed to reverseRange as it better describes
its purpose compared to the previous name reverseLine.
@noborus noborus merged commit c8eaa44 into master Jan 4, 2025
8 checks passed
@noborus noborus deleted the rename-func branch January 4, 2025 05:38
@@ -42,6 +41,7 @@ require (
github.com/spf13/cast v1.7.1 // indirect
github.com/subosito/gotenv v1.6.0 // indirect
go.uber.org/multierr v1.11.0 // indirect
golang.org/x/exp v0.0.0-20250103183323-7d7fa50e5329 // indirect
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm surprised to see a go.mod change when you are renaming a method

Copy link
Owner Author

Choose a reason for hiding this comment

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

I'm sorry. I'll be careful.

Copy link
Contributor

Choose a reason for hiding this comment

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

It's not a matter of being careful. I was simply curious why it changed

And yes, someone looking for commit history about a bug/change cause could be confused

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.

2 participants