We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
I think there is an error in solve_order() when after argument is passed as a list, it is filling before_l instead of after_l
solve_order()
after
before_l
after_l
pyvsc/src/vsc/constraints.py
Line 415 in 7accbb3
The text was updated successfully, but these errors were encountered:
I didn't realize you could pass lists to solve_order()! Easy fix, but might be good to add an example to the docs and a testcase with it.
Example:
@vsc.randobj class my_s(object): def __init__(self): self.a = vsc.rand_bit_t(1) self.b = vsc.rand_bit_t(16) @vsc.constraint def ab_c(self): vsc.solve_order(self.a, [self.b]) with vsc.implies(self.a == 0): self.b < 5 obj = my_s() obj.randomize(debug=True)
Debug snippet:
constraint ab_c { solve a,b before (a == 0) -> { (b < 5); } }
Sorry, something went wrong.
Fix solve_order's after argument when using lists
59c91c1
Addresses fvutils#213 Adds a unit test for the various ways to call solve_order. Update the solve_order docs with a snippet using lists.
No branches or pull requests
Hi,
I think there is an error in
solve_order()
whenafter
argument is passed as a list, it is fillingbefore_l
instead ofafter_l
pyvsc/src/vsc/constraints.py
Line 415 in 7accbb3
The text was updated successfully, but these errors were encountered: