Re: Re: Request to withdraw RFC's for nullable types foronly return values

On 4/28/16 4:41 PM, Björn Larsson wrote:

Can't resist jumping into this discussion, but when I first read both RFC's, I found them quite complementary.

In one sense, I agree. But when it comes to the question: let's vote on the options to decide what, if anything, happens to PHP, they are options with important differences. There's no way I can see to organize the vote that would be fair to everyone. For example, I prefer nullable returns only. I could settle for nullable hints/returns (NRH) as a second choice but I would prefer to make no change at all over union types. That being the case, I would want the voting to be structured in one specific way.

I was actually a bit tempted to combine them into one just as a writing exercise for my self (wanted to train on writing RFC's). My suggestion would be that you merge them into one and put it into vote quickly, maybe having you both as authors or one of you taking the lead?

I considered how this might work but I can't imagine how combining RFCs makes it easier. If more than one yes/no voting option is presented in one RFC, it's likely to be more confusing than voting on more than one RFC. Tom