-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Remove foreign function wrappers #8535
Closed
nikomatsakis
wants to merge
2
commits into
rust-lang:master
from
nikomatsakis:issue-3678-wrappers-be-gone-2
Closed
Remove foreign function wrappers #8535
nikomatsakis
wants to merge
2
commits into
rust-lang:master
from
nikomatsakis:issue-3678-wrappers-be-gone-2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@@ -30,7 +30,7 @@ Rust extras are part of the standard Rust distribution. | |||
#[crate_type = "lib"]; | |||
|
|||
#[deny(non_camel_case_types)]; | |||
#[deny(missing_doc)]; | |||
#[denyg(missing_doc)]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:(
@nikomatsakis - bitrotted. |
bors
added a commit
that referenced
this pull request
Aug 19, 2013
…, r=graydon Long-standing branch to remove foreign function wrappers altogether. Calls to C functions are done "in place" with no stack manipulation; the scheme relies entirely on the correct use of `#[fixed_stack_segment]` to guarantee adequate stack space. A linter is added to detect when `#[fixed_stack_segment]` annotations are missing. An `externfn!` macro is added to make it easier to declare foreign fns and wrappers in one go: this macro may need some refinement, though, for example it might be good to be able to declare a group of foreign fns. I leave that for future work (hopefully somebody else's work :) ). Fixes #3678.
My goodness sir. Thank you. |
Woohoo! 💃 |
Sorry for question -- I'm completely new to Rust -- does this mean FFI calls have no overhead now (comparing to ordinary functions)? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Long-standing branch to remove foreign function wrappers altogether. Calls to C functions are done "in place" with no stack manipulation; the scheme relies entirely on the correct use of
#[fixed_stack_segment]
to guarantee adequate stack space. A linter is added to detect when#[fixed_stack_segment]
annotations are missing. Anexternfn!
macro is added to make it easier to declare foreign fns and wrappers in one go: this macro may need some refinement, though, for example it might be good to be able to declare a group of foreign fns. I leave that for future work (hopefully somebody else's work :) ).Fixes #3678.