Don't use a context-wrapper scoped-context-override when unnecessary #520
Assignees
Labels
Comments
eyalroz
added a commit
that referenced
this issue
May 20, 2023
… we can just use the context-handle-based scoped override
eyalroz
added a commit
that referenced
this issue
Jun 7, 2023
… we can just use the context-handle-based scoped override * Also, removing (now?-)redundant forward-declaration of `context::current::scoped_override_t`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have both
cuda::context::current::scoped_override_tandcuda::context::current::detail_scoped_override_t. We mostly use the latter in API function implementations, but - in some places we use the former. Why? Actually, no good reason. The way we construct them, this could trigger additional actions - e.g. primary context pushing; but we don't actually need that to happen. So, let's be uniform again.The text was updated successfully, but these errors were encountered: