v3.3.4

CSTParser v3.3.4

Diff since v3.2.4

Closed issues:

• Should errors in the base comparison fail the tests? (#158)
• Parsing error (#302)
• Parse error (#304)
• is_func_call can return nothing (#306)
• Expr constructor sometimes returns a Symbol, Bool, etc (#308)
• Too broad recognition of nonstd identifier in import (#310)
• Interpolation expands too much in import (#311)
• plus_minus, minus_plus are not recognized as unary ops (#317)
• New multi-dimensional syntax not parsed the same as Meta.parse (#320)
• JET self test (#321)
• Track the number of semicolons in multidimensional expressions (#323)
• peekchar error in Atom (#327)
• Parsing @doc macro with trailing newline errors (#328)
• Parsing error? (#333)
• Stop parsing when it occurs to lambda function assignment (#334)
• Return information about when state errored (#335)
• const field support (#336)
• Incorrect Parse in global statement (#339)
• Possible error in import parsing (#340)
• Parser error with raw string with $ followed by multiline string (#341)
• Incorrect parsing with global const ... (#342)
• CSTParser cannot parse for loops in a quoted macro (#345)

Merged pull requests:

• fix quote parsing in brackets (#303) (@pfitzseb)
• fix blockquote in array exprs (#305) (@pfitzseb)
• Fix is_func_call (#307) (@pfitzseb)
• rename Expr constructor to to_codeobject (#312) (@pfitzseb)
• Fix nonstdid parsing and $ parsing in import (#313) (@pfitzseb)
• fix parsing of multiple ' (#315) (@simeonschaub)
• fix bare interpolation of "type" in strings (#322) (@pfitzseb)
• Add missing operators and fix precedences (#324) (@BenPH)
• add peekchar for IOBuffer (#326) (@KristofferC)
• Fix at-doc parsing at EOF (#329) (@pfitzseb)
• fix at-doc at EOF again (#330) (@pfitzseb)
• Julia Package Butler Updates (#331) (@github-actions[bot])
• Documentation for the EXPR data structure (#332) (@c42f)
• Support const fields in mutable structs (#337) (@pfitzseb)
• A bunch of fixes (#338) (@pfitzseb)
• Adjust global const parsing (#344) (@pfitzseb)
• Maybe fix LS.jl#1100 (#346) (@pfitzseb)
• Fix generator for parsing (#347) (@pfitzseb)