[RFC] Property Accessors v1.2 : isset / unset "failable"

I'm opening up several new threads to get discussion going on the remaining "being debated" categories referenced in this 1.1 -> 1.2 change spec: https://wiki.php.net/rfc/propertygetsetsyntax-as-implemented/change-requests ------------------------------------------------------------------------ *isset / unset / attempted writes when no setter / attempted reads when no getter** * Stas suggested that since there is presently no cases where these can fail that with accessors these should never "fail." Three possible ways to go (maybe others):

1.      If all cases can be tested for during compilation, prefer

compile failures.

2.      Let the compilation occur and at runtime when a disallowed

action is attempted, emit a warning and move on.

3.      As is currently, either at compilation or at runtime we issue a

fatal error and stop execution (probably least preferable if at runtime) If "no failures" should be the way we want to go, then #2 or some derivative makes the most sense. ------------------------------------------------------------------------ Thoughts? -- -Clint