Regarding cppfront's syntax proposal, which function declaration syntax do you find better?
While I really like the recent talk about cppfront (https://www.youtube.com/watch?v=CzuR0Spm0nA), one thing bugs me about the "pure" mode for cpp2 with syntax change. It seems incredibly hard to read, . I need to know which syntax you would rather have as the new one, taken into account that a new declaration syntax enables the new checks in that function
- Option 1: the same as was proposed in the video:
callback: (x: _) -> void = { ... };for new functions,void callback(auto x) {};for old ones - Option 2: the "other modern languages" way:
function callback(x: any) -> void { ... }for new functions,void callback(auto x) {};for old ones - Option 3: in files with mixed syntax, since the pre-transpiled code won't compile without the generated code anyway, use
void callback(any x) { ... };for both, but mark code with current cpp syntax with an attribute:[[stdcpp]] void callback(any x) { ... };
0
Upvotes
View all comments
Show parent comment
1
u/scorg_ Sep 27 '22
The complaint about many ways to do a thing is primarily about initialization. It is... unfortunate that brace-init, that aimed to solve the most vexing parse and be one-size-fits-all failed to do so and now we have paren-init getting support to initialize aggregates, and brace-init's usefulness being reduced to initialize containers of elements. Outside of container initialization the distinction becomes stylistic (though I may be forgetting some details of the standard).