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

EscapeScope must chain off a parent Scope #4

Closed
dherman opened this issue Sep 24, 2015 · 1 comment
Closed

EscapeScope must chain off a parent Scope #4

dherman opened this issue Sep 24, 2015 · 1 comment

Comments

@dherman
Copy link
Collaborator

dherman commented Sep 24, 2015

For safety, we need to guarantee that an escaping handle will escape into a stack that has a live handle scope. To enforce this, we can simply make the run method a member method of Scope instead of a static:

scope.run(|innerScope| {
    ...
    innerScope.escape(handle)
})
dherman pushed a commit that referenced this issue Oct 7, 2015
@dherman
Copy link
Collaborator Author

dherman commented Oct 7, 2015

Fixed in 3c596a0

@dherman dherman closed this as completed Oct 7, 2015
kjvalencik added a commit that referenced this issue Jun 8, 2022
alshdavid added a commit to alshdavid-forks/neon that referenced this issue Jun 22, 2024
# This is the 1st commit message:

get_uv

# This is the commit message neon-bindings#2:

added AsyncContext and cx.spawn_async

# This is the commit message neon-bindings#3:

added async function registration

# This is the commit message neon-bindings#4:

tidy

# This is the commit message neon-bindings#5:

comments

# This is the commit message neon-bindings#6:

using futures

# This is the commit message neon-bindings#7:

using futures

# This is the commit message neon-bindings#8:

vendored libuv

# This is the commit message neon-bindings#9:

Incorrect settings
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

1 participant