SnoopJMar 16
This is your periodic reminder that `0xfor....real` is a syntactically-valid AND error-free #Python program
Show threadWattana's Place of BrainrotMar 16
@SnoopJ how does that get past the parser? And how does it work?
Show threadSnoopJ
@Atirut it lexes the same as: `0xf or ....real` and the first part of the boolean OR is truthy, so short-circuit returns 15 without ever evaluating the RHS which would lead to an `AttributeError` if evaluated
Mar 16 at 4:54amWeb
Show threadWattana's Place of BrainrotMar 16
@SnoopJ ahhhh, I think that's what happens when the lexing logic is "consume until no hex characters" and not "consume until no hex characters AND check if it's a proper token boundary".
Show threadSnoopJMar 16
@Atirut yep. Modern versions of the runtime emit a SyntaxWarning for this kind of implicit boundary, perhaps it will become an error in the future
Show threadsabikMar 16

@SnoopJ @Atirut
`0xf or ....real` surely?

the first three dots are Ellipsis, so it's equivalent to `0xf or Ellipsis.real`

Show threadSnoopJMar 16
@sabik @Atirut oops, yes, I transposed those, thanks for the correction