Andrew Pinski
Andrew Pinski
> The best way to express writing/reading from a field of such type is to use _, e.g: Why not ... (aka the default value) instead of don't care? See...
> @apinski-cavium Could you provide a link or other reference to your suggestion in the 2022-Aug-08 LDWG meeting that was something along the lines of "when read, these fields behave...
So I just checked the reference compiler and noticed the name resolution of the return type is done with the type specialization but that looks a bit odd.
Oh so it looks like type keyword is the issue here, for some reason I thought type was not a keyword when I was writing the example case :). I...
Also I see why: ``` typedef bit type; ``` is accepted is because the grammer says to use name. name includes some keywords via nonTypeName. So either we need to...
A related example to this is: ``` extern void f(int t); void g(bit t) { f(t+0); } ``` Right now the reference compiler accepts the above when "+0" is removed...
Yes I don't see why can't signed types be valid here? (the bitwise operators are valid for fixed signed integer types even). For serializable enum case, should it decay to...
> changing boost::filesystem to std::filesystem I assume we already require GCC 9 ...
> > I assume we already require GCC 9 ... > > Not quite sure what you mean by that? GCC 9 should support std::filesystem, no? Before GCC 9, std::filesystem...