-
Notifications
You must be signed in to change notification settings - Fork 178
Document the simulator #1374
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
Document the simulator #1374
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1374 +/- ##
==========================================
+ Coverage 90.99% 91.09% +0.09%
==========================================
Files 45 45
Lines 11218 11302 +84
Branches 2429 2763 +334
==========================================
+ Hits 10208 10295 +87
+ Misses 831 830 -1
+ Partials 179 177 -2 ☔ View full report in Codecov by Sentry. |
10f7a35
to
45ed83e
Compare
3f6265f
to
52b12a6
Compare
This causes one test to fail due to a now-exposed bug. Co-authored-by: Wanda <[email protected]>
57743d9
to
bf905ad
Compare
This commit includes additional non-documentation changes, related to issues found while documenting it: - `Simulator.run_until()` no longer accepts a `run_passive=` argument. Passive no longer exist and in any case defaulting to `False` does not make a lot of sense from an API perspective. - `add_clock()`'s `phase=` argument, when specified, no longer has `period/2` added to it. This wasn't the documented behavior in first place and it makes no sense to do that. - `add_clock()` raises a `NameError` if a clock domain does not exist, instead of `ValueError`. - `add_clock()` raises a `DriverConflict` if a clock domain is already being driven by a clock, instead of `ValueError`. - GTKWave is no longer a part of the installation instructions, and both Surfer and GTKWave are recommended (in this order).
bf905ad
to
baf3b73
Compare
7870eb3
Rendered