Dave McEwan

I think sv-parser does the correct thing here. The correct syntax is `module snitch import snitch_pkg::*, riscv_instr::*; #(`. In the LRM (IEEE1800-2017), page 697 shows an except from Annex A,...

This looks like a bug to me. See #58.

@atyrberg Would you mind making a draft PR or branch with a testcase? Perhaps by adding some checks to test2: https://github.com/dalance/sv-parser/blob/master/sv-parser-pp/src/preprocess.rs#L919

Thanks, I see what you mean now, but I'm not sure of an immediate fix.

@tux3 Although it isn't a fix, I have found the comma-leading style helps for new code: https://github.com/DaveMcEwan/dmpvl/blob/master/prs/shr/sv/style_commaleading.sv

@SeanMcLoughlin Is this still a problem? Can you describe your usecase? You don't need to recompile sv-parser every time you want to run svlint.

@CaulyKan We need a bit more information here: 1. What do you expect? 2. Can you share your full testcase so I can reproduce what you see. FWIW those fragments...

You're right, this is confusing. @vasilissoti and I have seen a similar issue in [svdata](https://github.com/DaveMcEwan/svdata). I think this needs to be handled further downstream because sv-parser adheres closely to the...

This isn't an "easy" feature. Despite the language being backwards compatible, the formal specifications in Annex A are not fully compatible. To see what I mean, have a look at...

Related new rules: - `style_operator_arithmetic` - end (0 space) - 1space end - 1space comment - newline - `style_operator_boolean` - 1 space - `style_operator_unary` - end (0 space) - `style_operator_integer`...