You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the definitions of struct and enum types the comma is used as separator between struct/enum members. In the definition of traits the semicolon is used instead. I think this syntax is inconsistent and should be changed to allow comma as separator for traits as well.
An intuitive explanation might be, that you enumerate things when using a comma, like struct members or even function arguments. The definition of a trait is also an enumeration of methods.
IMO there is no need to use the C++ish syntax here (but maybe there are parsing pitfalls which enforce the semicolon here).
The text was updated successfully, but these errors were encountered:
This is bikesheddy, but I do think it might be a net win in consistency. In any case there's not much to argue over here, so an executive fiat would be nice.
If you mean separating the function signatures, then semicolons. The closest syntactic symmetry is with function signatures in extern blocks -- only other place we write signatures without bodies.
In the definitions of struct and enum types the comma is used as separator between struct/enum members. In the definition of traits the semicolon is used instead. I think this syntax is inconsistent and should be changed to allow comma as separator for traits as well.
An intuitive explanation might be, that you enumerate things when using a comma, like struct members or even function arguments. The definition of a trait is also an enumeration of methods.
IMO there is no need to use the C++ish syntax here (but maybe there are parsing pitfalls which enforce the semicolon here).
The text was updated successfully, but these errors were encountered: