You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This gives unexpected token on the ==. But if you change foo to use explicit return, with a semicolon after it, or if you put the binary equals expression inside of an assert, it appears to work fine.
I believe this is because the parser sees { and that means that the {true} is parsed as a block; in the other two instances, i.e. return {true} == true; and assert!({true} == true), the surrounds force {true} == true to be parsed as an expression, which works.
This gives unexpected token on the
==
. But if you change foo to use explicit return, with a semicolon after it, or if you put the binary equals expression inside of an assert, it appears to work fine.The text was updated successfully, but these errors were encountered: