[unsafe] Replace fs::File with libc::FILE#135
Merged
Conversation
This file contains hidden or 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
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.
Currently we translate
FILE*as*mut std::fs:FILE. This makes it difficult to translate functions such as feof and ferrror.feof and ferror both peek the internal state of the FILE object. std::fs::File doet not keep an internal state, it propagates the error right at the point of the usage, for example when performing a read or a write. On the other side,
*mut libc::FILE, which is the direct FFI equivalent ofFILE*, keeps the internal state, making the translation of feof and ferror easy.Another advantage of switching to
*mut libc::FILEis that it simplifies all stdio.h rules. For example fwrites becomes a simple call tolibc::fwrite, instead of the hand-rolled implementation that we have now for writing a buffer intostd::fs::File.