Naoya Hatta

@sabbellasri Thank you for your interesting in this issue.

Thanks. The issue seems to occur on all platforms. I'll investigate it. https://github.com/async-rs/async-std/issues/1055 https://github.com/tokio-rs/tokio/issues/5535

The broken links was fixed at the upstream repo. It will be reflected at the next submodule update.

I agree that parser generally should treat operator precedence. But the missing of operator precedence is intentional decision. At the early phase of development, I tried to add operator precedence....

Previous PR moved `write_tsv` from `src/main.rs` to `src/lib.rs`. Could you resolve the conflict?

Probably No. If you want to discuss about it, the following repository may be more appropriate. (Of course, you can use your own repository) https://github.com/actions-rs/meta

@md-rehman @JSH32 I've opened https://github.com/rust-lang/mdBook/pull/2286. It is a complete guide including syntax highlighting for custom playground.

I tried lsp testing based on https://github.com/ebkalderon/tower-lsp/issues/355#issuecomment-1484060565. https://github.com/veryl-lang/veryl/blob/master/crates/languageserver/src/tests.rs In the above test, `TestServer` implementation may be reusable. A minimal test code will become like below: ```rust #[tokio::test] async fn initialize()...

I think this PR can be merged. Could you resolve the conflict?

> As discussed briefly https://github.com/dalance/svlint/pull/224#issuecomment-1422900590, it would be nice to have rules for different levels of SystemVerilog abstraction. I agree the proposed levels. > Restart development on svdata (or its...