-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simulator throws an exception instead of returning X values on undefined RAM signal #15
Comments
Note that this bug doesn't affect all "compound" signal types:
this results in both
|
(apologies for the accidental close-and-reopen) |
The above suggests a workaround: if we have
then
|
The exception is coming from the
There's no easy way to fix this since |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems in certain circumstances, undefined values in RAM spoil the whole thing, not even into a fully-undefined signal, but one that throws an exception.
Here's a repro case on 0.2.4. Consider the following module:
If we look at
rv1
andrv1'
, we can see thatrv1'
takes on undefined (X
) values as expected:However,
rv1
crashes:The text was updated successfully, but these errors were encountered: