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
{{ message }}
This repository was archived by the owner on Jun 29, 2026. It is now read-only.
[{variable identifier 0 1} {operator := 2 4} {number int_literal 5 6} {operator / 7 8} {operator / 8 9} {variable identifier 10 13}]
(in the captures slice, the 1st one is the capture, the 2nd one is the node type). So it looks like it interprets // as two division operators instead of a start of a comment.
From what I can tell, trailing comments are accepted, as I see them in the Risor examples.
Given:
The generated parse tree is:
(source_file (short_var_declaration left: (expression_list (identifier)) right: (binary_expression left: (int_literal) (ERROR) right: (identifier))))and the captures are:
[{variable identifier 0 1} {operator := 2 4} {number int_literal 5 6} {operator / 7 8} {operator / 8 9} {variable identifier 10 13}](in the captures slice, the 1st one is the capture, the 2nd one is the node type). So it looks like it interprets // as two division operators instead of a start of a comment.
From what I can tell, trailing comments are accepted, as I see them in the Risor examples.