-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
fix(exercises): Does not follow the function naming convention snake_case #854
Conversation
snake_case
snake_case
In this case it'd be okay to change the offending function names too, since it's against convention and may confuse people that encounter it. |
is_FooBar rename is_foo_bar ? @diannasoriel |
If the problem is not fixed, there is a warning message |
Yes, that sounds right. |
Yes, I also encountered this warning problem. when will this commit merge into master branch? @diannasoriel |
Again, I would rather fix the problem properly than rely on suppressing the warning. Therefore, changing the non-snake-case function names to snake-case names would be the correct solution here. |
Has been modified according to snake-case: |
@all-contributors please add @xuesongbj for content |
@diannasoriel I've put up a pull request to add @xuesongbj! 🎉 |
Co-authored-by: zhangshaozhi <zhangshaozhi@ZhangshaozhideMacBook-Pro.local>
Co-authored-by: zhangshaozhi <zhangshaozhi@ZhangshaozhideMacBook-Pro.local>
Co-authored-by: zhangshaozhi <zhangshaozhi@ZhangshaozhideMacBook-Pro.local>
Co-authored-by: zhangshaozhi <zhangshaozhi@ZhangshaozhideMacBook-Pro.local>
This exercise does not follow the snake_case specification, cargo test has the following warning:
warning: function
is_FooBar
should have a snake case name.To ensure the meaning is correct, try to add allow non_snake_case.