Wilson Snyder

@Christian-Hecken how's this looking, is it ready for another review? If so can you click "resolved" on all of the feedback items that seem appropriate. Note to myself, this also...

Thanks, I agree with all your comments. Note that strictly IEEE allows only forcing of net types (6.5), and net types must be 4-state compatible (6.7.1), thus strings are not...

Is this good to merge? I'll run the rtlmeter just in case it trips on something which is unlikely.

Realized we're missing a piece, can you please update these files to use the force? ``` test_regress/t/t_uvm_dpi.v (Add real test where see uvm_hdl_force/uvm_hdl_release) test_regress/t/uvm/v2017_1_0/dpi/uvm_hdl_verilator.c test_regress/t/uvm/v2020_3_1/dpi/uvm_hdl_verilator.c (will be same edit as...

>and at least one failed because the usage of std::process was added to the function that is used on the RHS of the parameter assignment and as a result, that...

If you think this is ready please merge in master, fix conflicts, and let me know and will give it another review pass, thanks.

What change does this git bisect to? Can you attach a self-contained test case?

WIth --debug I get a much clearer `%Error: Internal Error: t/t_0.v:52:45: ../V3Ast.cpp:1196: AstDot must have non nullptr lhsp() ` I tried a few revs like last stable point and this...

Ok, so basically the small test case has always failed. The double :: might be painful to fix. Did you try using --debug on gca0a67941 with the full original test...

Messages crossed, that's a yes ;) Might you look into fixing this? Presumably V3LinkDot is what needs help.