Skip to content

Fix connect! #55

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

Merged
merged 1 commit into from
Jan 14, 2021
Merged

Fix connect! #55

merged 1 commit into from
Jan 14, 2021

Conversation

timholy
Copy link
Member

@timholy timholy commented Jan 1, 2021

connect! did the opposite of what was described in the docstring.
The docstring is more consistent with the convention of the modified
argument being first, so we go with the docstring and change the code.

While technically this is a bugfix, it could trigger StackOverFlow
errors, so let's call this a breaking change.

@timholy
Copy link
Member Author

timholy commented Jan 4, 2021

As a heads-up, I have a whole bunch of other changes queued, but to avoid having to constantly resolve merge conflicts I'll submit them sequentially.

I'm not exactly sure how the sequence should relate to released versions; by the time the series is done, I think it would be reasonable to consider a 1.0 release.

`connect!` did the opposite of what was described in the docstring.
The docstring is more consistent with the convention of the modified
argument being first, so we go with the docstring and change the code.

While technically this is a bugfix, it could trigger StackOverFlow
errors, so let's call this a breaking change.
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