-
Notifications
You must be signed in to change notification settings - Fork 8
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 get_{sender,receiver}
to new_{sender,receiver}
#49
Rename get_{sender,receiver}
to new_{sender,receiver}
#49
Conversation
get_{sender,receiver}
to new_{sender,receiver}
2d08227
to
b0a18d7
Compare
Rebased, ping @sahas-subramanian-frequenz |
* Channels methods `get_receiver()` and `get_sender()` have been renamed to | ||
`new_receiver()` and `new_sender()` respectively. This is to make it more | ||
clear that new objects are being created. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be listed under Breaking changes
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a (breaking changes)
to Upgrading
to make it more clear that this section list breaking changes. We can change the template if Upgrading
is not clear enough. I used this to make it clear for people writing notes that it is important to say how to upgrade from breaking changes, not just listing them.
Using `get_` as a prefix gives the idea that one is always getting the same object, but these methods are indeed creating new objects. Signed-off-by: Leandro Lucarella <[email protected]>
ee3963d
b0a18d7
to
ee3963d
Compare
Using
get_
as a prefix gives the idea that one is always getting the same object, but these methods are indeed creating new objects.