Re: The @@ is terrible, are we sure we're OK with it?

On Wed, Jul 22, 2020 at 4:29 PM Sara Golemon <pollita@php.net> wrote: > Citation Needed. > > The '@' token and the T_DOUBLE_AT token come from the lexer as distinct > values, where is the conflict? > > I'm not doubting that there is one, you're quite clever, but at the moment > you're stating facts not currently in evidence. > > So evidently, this is specifically an issue with attributes in places where a portion of their name could be mistaken for a type. AIUI, that's being addressed. So the complaint is "what if moar ambiguity?" ? Seems like we're trading a lot of ambiguities. @@ might be a double error suppress (and might spill over types) #[..] might be a legit comment <<...>> might be a freaky combination of bit shifts Regards the vote; I don't believe that @@ has been proven unworkable, however if I'm wrong about that, then the second choice selection from the last vote would obviously take precedence. -Sara