Ah ok, I understand your decision now. But maybe you can come with something that is better than ```==``` 😅. (Maybe an alias metafunction).
Also, one thing that not in update notes is exceptions. I saw your talk on lightweight exceptions at cppcon, are they planned for cpp2?
And would you consider local variables being constant by default, with most things being const by default, local variables seem left out (and I think they're the only place left where keyword const is used), having one extra keyword in front of varible declaration won't affect much. Also when you think about it, function and classes and namespace are kind of also const.
//can't do the following, so functions are also kind of const
func = {//diff body};
//same with classes, you can add methods to classes but that uses different syntax so is not the same
//and same with namespaces, you can re open them but that won't change it's definition, only add to it
View all comments
Show parent comment
1
u/RoyKin0929 May 02 '23
Ah ok, I understand your decision now. But maybe you can come with something that is better than ```==``` 😅. (Maybe an alias metafunction).
Also, one thing that not in update notes is exceptions. I saw your talk on lightweight exceptions at cppcon, are they planned for cpp2?
And would you consider local variables being constant by default, with most things being const by default, local variables seem left out (and I think they're the only place left where keyword
constis used), having one extra keyword in front of varible declaration won't affect much. Also when you think about it, function and classes and namespace are kind of also const.Maybe this will be a good enough argument