On Tue, Jul 10, 2018 at 11:18 AM, Marco Pivetta <ocram...@gmail.com> wrote:
> It's been a few weeks since this has first landed here, and we're just > wasting time in relatively silly discussions at this point: > > - As I said earlier, this patch has already been tested against some > extremely tricky scenarios, so from a userland perspective it is safe for > inclusion. If you don't have confidence in something related to it, please > write a test case and help out. > Thanks a lot for your tests and feedback! > - can we get a yes/no from the RMs on whether we'll have the time window > to (potentially) get this voted and (*if* passed) merged? Shoot out a mail > with the decision, please. We could have a vote for which version to > include this in, if that's really such a big issue. > - can we split out discussions on 8.0 scope? Minor versions are indeed for > features. If PHP 8.0 lacks interesting/marketing features, that's a > different story. > - Nikita/Bob: can this be voted upon right after the RMs have taken a > decision? Anything blocking missing? > I've just updated the RFC with the last major change (switch to the "no intrinsic types" alternative for reference handling). Apart from some minor tweaks (maybe add a bit more information on how the implementation works) the RFC itself should be about ready for voting. Even if the RMs decide that this cannot go into PHP 7.3, we'd still like to start voting on this RFC soon (in the next few days). - Is the reference issue reported by Nicolas a blocker? Nicolas, can you > clarify here? > My plan for the reference reflection would be to write a separate RFC. While typed properties make this more important, the feature itself is really independent, and while we could slip it through as part of this RFC, I think that this problem has a large enough design space that we should discuss it separately. Nikita
