This repository has been archived by the owner on Jul 5, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 843
Hide Circuit
implementation of sub-circuits behind test
feature
#953
Labels
T-tech-debt
Type: tech-debt generated or cleaned up
Comments
I'm totally in favor of that change! |
Hi, I can do it. |
NOTE that Assigning to @ChengYueJia then! |
@han0110 @ChengYueJia Doesn't SuperCircuit get used outside the tests to run the actual system? |
Yes, |
But then, my question is SuperCircuit uses the Circuit implementation of the other SubCircuits: so all these, should not be only in the tests, but also in production, right? |
But |
hero78119
pushed a commit
that referenced
this issue
Apr 10, 2023
### Issue Link * First mentioned in #953 * Pr link This is the second pr for this. The older one #1003 is abandoned as there are too much conflicts. ### Contents * Gather test related into test mod. * Gather most of the `impl Circuit` into `dev.mod` This is for distinct the `test-circuits` and the test features. #1144
Resolved via #1300 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
After #937 we no longer need the implementation
Circuit
for sub-circuits in production, it's only required for test and cratescircuit-benchmarks
to benchmark individual sub-circuit, so we should move current implementation into#[cfg(any(feature = "test", test))] mod test { ... }
to avoid further consumers to use them accidentally.The text was updated successfully, but these errors were encountered: