Max Korbel

## Motivation The `_execute` function in `Combinational` currently drives all outputs to `x`, then executes the conditionals. This is less efficient than it could be, since `Conditional.execute` returns a list...

Replace generic `Exception`s with more specific or ROHD-related exceptions

2

## Motivation Many exceptions in ROHD are just `Exception`, but they should be more specific types of exceptions or ROHD-specific `Exception`s. ## Desired solution Add new ROHD-specific `Exception`s where applicable,...

## Motivation If someone uses the same `Conditional` object multiple times in the same `_Always` or in different `_Always` blocks, it can cause unexpected behavior and simulation/synthesis mismatches. ## Desired...

## Motivation There should be extremely robust testing around X/Z optimism/pessimism, especially around conditional logic and `_Always`. ## Desired solution Add more tests covering different scenarios

## Describe the bug The `CaseZ` matching logic checks for `LogicValue` equality, which includes comparing `z` and `x` invalid values. If a non-constant floating signal is used as an input...

Create a utility that can convert SystemVerilog modules into ROHD

1

## Motivation There is a lot of legacy SystemVerilog code. ROHD offers a lot of benefits, not all of which are entirely realized purely through cosimulation. ## Desired solution Something...

## Motivation Build-time uses signal connectivity to derive hierarchy, so new connections after build could cause strange mismatches between generated code and simulation behavior. Similarly, if signals are connected after...

## Motivation Currently, you can only connect each `Logic` to one source ever, and then it cannot be reassigned to connect to something else. There are cases where it might...

Make `Logic`'s `toString()` method more insightful

4

## Motivation The current `toString` for `Logic` just gives the type, name, and width. It could be more insightful than that. ## Desired solution It could show more information including...

## Motivation With the current implementation, if a signal is being listened to for `changed`, then it triggers an action on every `preTick` and `postTick` of the simulator. This is...