Hi Sara, I'd like to explain my rationale. Most of the time I end up using "#[todo] Whatever" while documenting my code... my intentions are "# [todo] ...", but you know... missing that space char doesn't break anything today... In any case, BC is broken and FC would also not work. Now I assume it's a quite rare scenario where someone is doing: @[...] where suppressing is needed, especially when we check against the #[...] case.
Cheers, On Tue, Aug 11, 2020 at 10:55 AM Sara Golemon <poll...@php.net> wrote: > > On Mon, Aug 10, 2020 at 3:41 AM Derick Rethans <der...@php.net> wrote: > > > https://wiki.php.net/rfc/shorter_attribute_syntax_change#voting > > > > > Just chiming in to say all, y'all voting for @[...] are making a terrible > choice, and are you sure you're okay with it? > > We have options with varying degrees of backward compatibility issues (<<>> > none, @@ some, #[..] and @[..] a bit more than some), and only one which > offers forward compatibility (#[..]). > So why vote in favor of the option with the highest BC breaking probability > and no FC? > > Thank you for coming to my TED talk. > > -Sara -- Guilherme Blanco SVP Technology at Statflo Inc. Mobile: +1 647 232 5599 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
