Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Document control flow limitations of global tracers #143

Closed
adrhill opened this issue Jul 25, 2024 · 1 comment · Fixed by #175
Closed

Document control flow limitations of global tracers #143

adrhill opened this issue Jul 25, 2024 · 1 comment · Fixed by #175
Labels
documentation Improvements or additions to documentation

Comments

@adrhill
Copy link
Owner

adrhill commented Jul 25, 2024

Document why TracerLocalSparsityDetector/Dual support control flow and why TracerSparsityDetector/AbstractTracer don't.

The need for this has popped up at least twice:

It would also be nice to explain intricacies of ifelse and workarounds via custom overloads.
@adrhill adrhill added the documentation Improvements or additions to documentation label Jul 25, 2024
@adrhill adrhill mentioned this issue Jul 25, 2024
Merged
@adrhill adrhill mentioned this issue Aug 16, 2024
Closed
@adrhill
Copy link
Owner Author

adrhill commented Aug 16, 2024

In the meantime, some information on SCT's design can be found here: #172 (comment)

@adrhill adrhill mentioned this issue Aug 20, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation Improvements or additions to documentation
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Document limitations adrhill/SparseConnectivityTracer.jl
1 participant
@adrhill