-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Rust does not allow trailing commas in a fn signature #6506
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
Comments
Yeah, it would be consistent, maybe it could useful in macros, but ... ew. |
I agree with @brson 's "ew", and I would much rather declare that commas are always element separators, but I guess we should discuss. Nominating for milestone 1, well-defined. |
Accepted for well-defined |
I think it ought to be consistent. It looks ugly in that example but it is useful for macros and, if you put |
Triage. This was discussed in the meeting, and the decision was to allow trailing commas. |
… r=Manishearth Lint "&PathBuf instead of &Path" in PTR_ARG fixes rust-lang#6502 changelog: lint "`&PathBuf` instead of `&Path`" in `PTR_ARG`
I think this can be considered a bug, seeing how trailing commas generally are allowed at other places:
The text was updated successfully, but these errors were encountered: