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.

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

dip1008 compliant #23

Open
skoppe opened this issue Jun 23, 2021 · 1 comment
Open

dip1008 compliant #23

skoppe opened this issue Jun 23, 2021 · 1 comment

Comments

@skoppe
Copy link
Collaborator

skoppe commented Jun 23, 2021

During some asynchronous cleanup we sometimes have to take a hold of exception to rethrow them later, but this interferes with dip1008 scope assumptions.

For refcounted exception we should be able to incr/decr the refcount.

Statically or stack allocated ones are still an issue. We would need to clone them. But besides there not being a clone function on exceptions, it is likely hard to detect those exceptions.

@rmanthorpe
Copy link
Contributor

Why are statically allocated exceptions a problem? Their lifetime is the same as the lifetime of the program aren't they?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants