We are therefore going to proceed with
public private(set)
, the same
syntax as Swift and the current RFC text use.
It seems my previous email went to /dev/null.
This is incomprehensible.
Go with public(get) private(set) please.
"public private" makes no sense.
We are therefore going to proceed with
public private(set)
, the same
syntax as Swift and the current RFC text use.It seems my previous email went to /dev/null.
This is incomprehensible.
Go with public(get) private(set) please.
"public private" makes no sense.
The Swift-style syntax should be read as "public visibility for all operations unless otherwise specified, and then specify private for set". Should some other operation be broken off as individually controllable in the future, the syntax will expand to support it without further complication.
--Larry Garfield