Re: RFC: constructor argument promotion

Hi Sean, thanks for your answers. Am 08.08.2013 um 02:54 schrieb Sean Cannella <seanc@fb.com>: > It does in the sense the same way as the current mode "enforces" types on > properties. That is, there's no guarantee that types will remain as > initially set, only that the values passed to the constructor must be X > type, ergo the post-ctor values of the props will be of type X. I can see > the argument that it suggests real (permanent) typing where none exists > though. [...] Makes sense. Given that, I don’t feel the shorter syntax is worth the WTF :) cu, Lars

Attachment: [application/pgp-signature] Message signed with OpenPGP using GPGMail signature.asc