> > >> I agree that there is a use case for it, however I don't think the > proposed syntax `public:private` is intuitive. Maybe we can come up with > something better? >
Would something closer to Swift be better? If so I expanded the RFC with
that syntax option as well:
class User {
public private(set) int $id;
public protected(set) string $name;
public function __construct(int $id, string $name) {
$this->id = $id;
$this->name = $name;
}}
