AFAIK, creating latches is just as easy in Verilog as in VHDL. They use the same model to determine when to create one.
But with a solid design flow (which should include linting tools like Spyglass for both VHDL and Verilog), it’s not a major concern.
SystemVerilog basically fixes this with always_comb vs always_latch.
There's no major implementation which doesn't handle warning or even failing the flow on accidental latch logic inside an always_comb.
Re:VHDL's Crown Jewel
by hrmtst93837 on Monday March 30, 2026 @04:03AM
(#47571661)
Verilog gives you enough rope.
Once the design gets past toy size, you spend time chasing sim vs synthesis mismatches because the language leaves ordering loose in places where humans read intent into source order.
VHDL's delta cycles are weird, and there's edge cases there too, but the extra ceremony works more like a childproof cap than a crown jewel.
That does sound like my experience…
> Once the design gets past toy size,
Do you consider 800+mm2 slabs of 3nm of silicon still toy size? Because there's a very high chance that those were written in Verilog, and I've never had to chase sim vs synthesis mismatches.
> Verilog gives you enough rope.
Yes. If you don't know what you're doing and don't follow the industry standard practises.
(System)Verilog has delta cycles too you know, they call it an event queue, but it's basically the same. It's the direct variable updates that happen outside of this mechanism that cause all the issues. Imho it was a poor attempt at simulation optimization, and now you can't take it out of the language anymore.
((Shai-Hulud Desires the Verilog))