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
Change affect_neg!
keyword arg to instead be a different constructor
#18
Comments
Right! I thought about that. Well, it's only a keyword, isn't it? The function itself will still be mutating function. |
Yeah, but the name should probably be consistent. If the keyword arg is |
I agree. Or not letting
or something like that. |
I like that suggestion a lot. I think that's the correct way forward. |
affect!
for affect
affect_neg!
keyword arg to instead be a different constructor
I implemented this suggestion. There is a depwarn telling people to look at the docs if they use the kwarg, and the docs are being updated right now. I'll tag a new version with this soon. |
While it seems odd to get rid of
!
on a mutating function, @ccontrer 's example brings up a big issue:That works.
That errors. See the difference? Julia parses
affect_neg!=affect_negative!
asaffect_neg
!=
affect_negative!
, and errors. That's not nice behavior, and so I think it might be best to just take off the!
.The text was updated successfully, but these errors were encountered: