-
Notifications
You must be signed in to change notification settings - Fork 1.1k
add fmemopen, open_memstream, and open_wmemstream for POSIX.1-2008 #1855
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
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @JohnTitor (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
CI says:
but I think the aarch64 env already has them, doesn't it? |
I tried to model off other POSIX.1-2008 functions and I don't understand why it would be missing only on aarch64. What's the procedure for fixing this? |
If it isn't missing, we can skip the tests for them in |
And I think it's related to #1765, it'd be great if you also could add a FIXME comment(s) with this issue number. |
@jedbrown Friendly-ping, we're going to a new release. If you're still interested, I'm happy to wait for a while until this gets merged :) |
Skip test on aarch64 due to rust-lang#1765
@JohnTitor Thanks for the ping. I've added it to the skip list for aarch64. Did you also want a comment in |
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.
Did you also want a comment in src/unix/mod.rs next to these functions? I don't see it for the other cases listed in libc-test/build.rs.
No, this makes sense now. Thanks!
This is useful for interfacing with C libraries that can write output to
FILE
objects, for example.