upvote
I worked for a couple of years in a SystemVerilog compiler, and I couldn't agree more with your sentiment.

From the compiler construction standpoint, it's grossly underspecified, to the point that our customers' designs were way more expressive than the spec.

And from the users' perspective, it's confusing, quite limited, and you end up having to resort to hacks to achieve what should be part of the language... Fortunately I can't remember any particularly bad examples, it's been 15 or so years since I left for greener pastures.

Still, I sometimes wonder, how much of HW design is influenced by the language decisions, these ugly hacks, and the emerging (System)Verilog design patterns? Could it be measurably better in a different world?

reply
Yeah, using (system)verilog is essentially a process of "think of the digital circuit you want, then figure out how to write it as a 'sequential' process so that the compiler can then generate the circuit you want". The way it works feels quite clever when you first learn about it but the way it works in practice is bizarre.
reply
Could we fix that do you think?

I think 25 years ago I would not have believed we would ever fix (La)TeX but here's Typst.

reply
Will I have the same learning effect if I use https://github.com/clash-lang/clash-compiler instead of straight verilog, or is the language a necessary part of it?
reply
As the maintainer of clash I would say yes definitely! Clash is at the same level of hardware specifications as VHDL and verilog. You lay down every wire and register. It's just that you get all the niceties of Haskell, the very powerful type system and abstraction capabilities.
reply
It's awful by design! Do you know how much Cadence, Synopsys, and Siemens profit off of the bloated LRM?
reply