On 05/22/2016 02:26 PM, Paolo Carlini wrote:
finally sending a patch for this issue. As noticed by submitter himself, it appears to boil down to a rather straightforward case of not rejecting unexpanded parameter packs in default arguments. In order to handle all the combinations (in/out of class, template parameter/function parameter) I added calls of check_for_bare_parameter_packs both to cp_parser_default_argument and cp_parser_late_parsing_default_args
Hmm, would it make sense to check in cp_parser_initializer? Jason
