chisel2-deprecated icon indicating copy to clipboard operation
chisel2-deprecated copied to clipboard

Failure to specify a default to a wire no longer gives meaningful error message

Open sdtwigg opened this issue 11 years ago • 1 comments

Previously, failure to specify the default for a wire (when using whens and similar) would give an error message indicate, at the very least, the name of the offending wire. Now, a NullPointerException is thrown in the width inference phase. The stack trace gives no meaningful info to the user.

sdtwigg avatar Nov 25 '14 06:11 sdtwigg

Did you try it with the latest master? It should tell you problematic wires. Please refer to #339

donggyukim avatar Nov 25 '14 18:11 donggyukim