Hi, Welcome back, Andrea! It's great to see you contributing here again :)
2015-10-28 21:08 GMT-03:00 Andrea Faulds <a...@ajf.me>: > Hi everyone, > > It’s been two weeks, so voting on this RFC can start. The rules are as > usual. This is a language change, so a 2/3 majority is required. > > The vote can be found here: > > https://wiki.php.net/rfc/void_return_type#vote > > Voting starts today (2015-10-28) and will end next Sunday (2015-11-08), 10 > days’ time. > > Thanks! > -- > Andrea Faulds > http://ajf.me/ > I just voted -1 because "null" is the optimal solution for PHP, not "void". To summarize: 1) functions declared with "void" return type will still return "null", so "void" is a big fat lie for PHP while "null" is currently accurate. 2) "null" is already reserved, this is a minor detail but it does make a difference as it's the zero BC break path. 3) "null" interacts much better with the union types RFC 4) "null" would have practically the same effects on enhancing interfaces as "void", so "null" still preserves the RFC intentions. So my thoughts pretty much echoes Levi, Bob and the others that questioned the void choice during the discussion phase. Even though I'm still in favor of a way to specify that functions shouldn't return a value other than "null", "void" feels inaccurate and perhaps even poorly justified. Thanks, Marcio. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
