On Monday, 1 October 2018 at 04:22:24 UTC, Manu wrote:
Ah, good point. So, it could only be allowed if scope...
struct Bob
{
void setThing() shared scope;
}
That's going to require far-reaching proliferation of `scope`.
Do we infer `scope` like the other attributes?
For templates (either the function or the struct it is in) and
auto returning functions, I think so: definitely under -dip1000,
probably also when not using -dip1000.
The default for `scope` is totally backwards. :/
Alas, such is the nature of retrofitting.