OK.
On Wed, Oct 18, 2017 at 7:07 AM, Paolo Carlini <paolo.carl...@oracle.com> wrote: > Hi, > > a rather straightforward issue that we didn't notice so far only because in > all our uses of __is_trivially_constructible either neither type is > dependent or both are (eg, in library uses). The below handles in the > obvious way a possible TREE_LIST - built node by node by > cp_parser_trait_expr in the variadic case - as TRAIT_EXPR_TYPE2. Tested > x86_64-linux. Seems suitable for the branches too. > > Thanks, Paolo. > > /////////////////////// >
