Re: [PATCH] [PR c++/71965] silence multi-dim array init sorry without tf_error

2018-03-21 Thread Alexandre Oliva
message: "array must be > initialized with a brace-enclosed initializer". > OK with that change. Thanks. Besides changing the message, I added the location of the initializer to the message. Here's what I'm checking in: [PR c++/71965] silence multi-dim array init sorry

Re: [PATCH] [PR c++/71965] silence multi-dim array init sorry without tf_error

2018-03-20 Thread Jason Merrill
initializer"); > >> This shouldn't even be a sorry anymore > >> Let's make it a hard error here. > > Like this? > > > [PR c++/71965] silence multi-dim array init sorry without tf_error > > We shouldn't substitute templates into short-circui

Re: [PATCH] [PR c++/71965] silence multi-dim array init sorry without tf_error

2018-03-20 Thread Alexandre Oliva
it a hard error here. Like this? [PR c++/71965] silence multi-dim array init sorry without tf_error We shouldn't substitute templates into short-circuited-out concepts constraints, but we do, and to add insult to injury, we issue a sorry() error when a concept that shouldn't eve

Re: [PR c++/71965] silence multi-dim array init sorry without tf_error

2018-03-20 Thread Jason Merrill
On Sat, Mar 17, 2018 at 8:11 AM, Alexandre Oliva wrote: > We shouldn't substitute templates into short-circuited-out concepts > constraints, but we do, and to add insult to injury, we issue a > sorry() error when a concept that shouldn't even have been substituted > attempts to perform a multi-dim

Re: [PR c++/71965] silence multi-dim array init sorry without tf_error

2018-03-17 Thread Alexandre Oliva
On Mar 17, 2018, Alexandre Oliva wrote: > We shouldn't substitute templates into short-circuited-out concepts > constraints, but we do, and to add insult to injury, we issue a > sorry() error when a concept that shouldn't even have been substituted > attempts to perform a multi-dimensional array

[PR c++/71965] silence multi-dim array init sorry without tf_error

2018-03-17 Thread Alexandre Oliva
We shouldn't substitute templates into short-circuited-out concepts constraints, but we do, and to add insult to injury, we issue a sorry() error when a concept that shouldn't even have been substituted attempts to perform a multi-dimensional array initialization with a new{} expression. Although