On 12/22/2014 04:51 PM, Paolo Carlini wrote:
Well, if they are both right, could we maybe do something closer to clang, instead, thus not consider the for loop a range-based for loop only because after the initializer there is a colon when the decl is error_mark_node?
I think we want to tell the user that you can't have an explicit initializer in a range-based for loop, since that's the mistake that they've made; that seems more helpful than saying you can't have a colon after a for-init-statement.
Jason
