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
the third comment, which doesn't parse and claims else is a variable, should be fine since else's Block is on its same line -- not like else \n { }, which is correct for being broken.
Also the second ok comment becomes not OK when there was a preceding elsif:
if/* ok */(){} /* ok */ elsif /* not ok */ (){# with elsif} /* errorsherenow */ else{}
but the comment before elsif is still legal. So it's quite specific.
You recently patched allowing almost arbitrary whitespace in if/else, I think the comments should be treated the same way -- unless it's not worth the implementation.
The text was updated successfully, but these errors were encountered:
catb0t
changed the title
Comments between elsif / else and their Block
Allow comments between elsif / else and their argument list or the last Block
Nov 8, 2018
catb0t
changed the title
Allow comments between elsif / else and their argument list or the last Block
Allow comments between elsif / else and argument lists / Blocks
Nov 8, 2018
the third comment, which doesn't parse and claims
else
is a variable, should be fine sinceelse
's Block is on its same line -- not likeelse \n { }
, which is correct for being broken.Also the second
ok
comment becomes not OK when there was a precedingelsif
:but the comment before
elsif
is still legal. So it's quite specific.You recently patched allowing almost arbitrary whitespace in if/else, I think the comments should be treated the same way -- unless it's not worth the implementation.
The text was updated successfully, but these errors were encountered: