Skip to content

Add .write(true) to append and truncate examples #26642

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

Merged
merged 1 commit into from
Jun 29, 2015
Merged

Add .write(true) to append and truncate examples #26642

merged 1 commit into from
Jun 29, 2015

Conversation

remram44
Copy link
Contributor

Setting append without write doesn't give you a writeable file. Showing it as an example in the docs is confusing at best (reddit)

Using truncate (O_TRUNC) on a read-only file is an error on POSIX systems ("unspecified"). Note however that using create (O_CREAT) with read-only flags is fine.

Related: #26103 (which IMHO is wrong; saying "append is different than write" when should simply be "append needs write". My vote is to make append imply write)

Setting append without write doesn't give you a writeable file. Showing
it as an example in the docs is confusing at best.

Using truncate on a read-only file is an error on POSIX systems (note
however that using create with read-only flags is fine).
@rust-highfive
Copy link
Contributor

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @brson (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. 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.

@alexcrichton
Copy link
Member

@bors: r+ 78ec055 rollup

bors added a commit that referenced this pull request Jun 28, 2015
…crichton

Setting append without write doesn't give you a writeable file. Showing it as an example in the docs is confusing at best ([reddit](https://www.reddit.com/r/rust/comments/3bbz8w/why_is_writing_a_file_not_working_for_me/))

Using truncate (O_TRUNC) on a read-only file is an error on POSIX systems ("unspecified"). Note however that using create (O_CREAT) with read-only flags is fine.

Related: #26103 (which IMHO is wrong; saying "append is different than write" when should simply be "append needs write". My vote is to make append imply write)
@bors
Copy link
Collaborator

bors commented Jun 28, 2015

⌛ Testing commit 78ec055 with merge 2671e8c...

@remram44
Copy link
Contributor Author

OpenOptions::new().open("foo.txt") in the doc for new() is also weird to me. open(2) specifies that "flags must include O_RDONLY, O_WRONLY, or O_RDWR", but in practice O_RDONLY is 0 so this actually does OpenOptions::new().read(true).open("foo.txt"), only in a sneaky way (not exactly dangerous).

@bors bors merged commit 78ec055 into rust-lang:master Jun 29, 2015
@remram44 remram44 deleted the doc-openoptions-missing-write branch June 29, 2015 00:04
remram44 referenced this pull request in steveklabnik/rust Jun 29, 2015
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

Successfully merging this pull request may close these issues.

5 participants