Re: [Swan-dev] type_t, type() and TYPE() in initializers

2019-01-19 Thread D. Hugh Redelmeier
| From: Andrew Cagney | On Sat, 19 Jan 2019 at 03:51, D. Hugh Redelmeier wrote: | > | > | From: Andrew Cagney | > It doesn't make sense to initialize a static with an assignment from | > an object. Amusingly, it does make sense to initialize a static with | > the address of a compound literal

Re: [Swan-dev] type_t, type() and TYPE() in initializers

2019-01-19 Thread Andrew Cagney
On Sat, 19 Jan 2019 at 03:51, D. Hugh Redelmeier wrote: > > | From: Andrew Cagney > > | I'm sure this has come up before - the discussion concluded that a > | cast within a static initializer probably isn't technically static. > > A compound literal starts with what looks like a cast but it isn'

Re: [Swan-dev] type_t, type() and TYPE() in initializers

2019-01-19 Thread D. Hugh Redelmeier
| From: Andrew Cagney | I'm sure this has come up before - the discussion concluded that a | cast within a static initializer probably isn't technically static. A compound literal starts with what looks like a cast but it isn't a cast. On the other hand, a compound literal actually creates an