Naoya Hatta

The criteria of adding a language is described at https://github.com/github-linguist/linguist/issues/5756. The current criteria is "at least 2000 files per extension". Now the result is 88. So I'll send the request...

I'm interesting in this feature. One of the dissatisfied points of Chisel was missing machine readable source map. The consideration points of this feature: * Where are there annotations? *...

I'm tring to add source map support at #741. I adopted the source map format of JavaScript defined at https://sourcemaps.info/spec.html. This is because the format has large ecosystem in JS...

I added a feature to remap `path:line:col` in verilator's log at `veryl test`. Now we can see where is root cause in Veryl's code easily. ``` %Error: /home/hatta/work/repos/veryl/testcases/sv/48_test.sv:11: Verilog $stop...

I'll merge #741, and this issue will be closed. The remaining features are moved to #776 because I think the feature to consume source map should be separated from Veryl...

Thank you for your suggestion. I'll consider about it.

Thank you for your suggestion. It seems to be good idea. But I don't have an experience about such conference, so it seems to be difficult...

Thanks. I'll consider to submit to such workshop at the next chance.

I agree that hierarchical structure is useful. I think there are some points which should be considerd. ### Explicit file structure Currently, Veryl gather "*.vl" files recursively from the directory...

Looks good. Which is better `enum logic` and simple `logic`? `enum logic` can check assignment without cast in SystemVerilog side. But I think the result of compare operator can't be...