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

Handle indirect spawns (and binding clones) #82

Closed
graydon opened this issue Jun 28, 2010 · 1 comment
Closed

Handle indirect spawns (and binding clones) #82

graydon opened this issue Jun 28, 2010 · 1 comment

Comments

@graydon
Copy link
Contributor

graydon commented Jun 28, 2010

We currently only know how to spawn a static function. Spawning an indirect (bind) should work, and should clone the binding. Of course this means supporting more lifecycle operations in bindings at all; presently they have neither clone nor drop support.

@graydon
Copy link
Contributor Author

graydon commented Jan 27, 2011

WONTFIX

keeperofdakeys pushed a commit to keeperofdakeys/rust that referenced this issue Dec 12, 2017
dlrobertson pushed a commit to dlrobertson/rust that referenced this issue Nov 29, 2018
dlrobertson pushed a commit to dlrobertson/rust that referenced this issue Nov 29, 2018
…s_chapter

Fix broken links in macros chapter (issue rust-lang#82)
eddyb pushed a commit to eddyb/rust that referenced this issue Jun 30, 2020
antoyo pushed a commit to antoyo/rust that referenced this issue Sep 28, 2021
* Correctly handle st(0) register in the clobbers list
* Gate the clobbers based on enabled target features
bors pushed a commit to rust-lang-ci/rust that referenced this issue Oct 1, 2021
This issue was closed.
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