https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.46.0 2020-07-11T06:26:34+00:00 2020-07-11T06:26:34+00:00 Manish Goregaokar manishsmail@gmail.com 2020-07-11T06:26:34+00:00 urn:sha1:427ef98bc3ed87190f389bebc64cc76604c0213a Add `read_exact_at` and `write_all_at` to WASI's `FileExt` This adds `read_exact_at` and `write_all_at` to WASI's `FileExt`, similar to the Unix versions of the same names. 2020-07-07T23:04:52+00:00 Dan Gohman sunfish@mozilla.com 2020-07-07T22:56:07+00:00 urn:sha1:58fc61b79cd15fdafad6e15991553f5c33422ade Rename the existing read_at/write_at to read_vectored_at/write_vectored_at, for consistency with libstd's read_vectored/write_vectored. And, introduce new read_at/write_at functions which take a single buffer, similar to all other targets which provide these functions, so this will make it easier for applications to share code between WASI and other targets. Note that WASI's FileExt is currently unstable. 2020-07-07T23:04:52+00:00 Dan Gohman sunfish@mozilla.com 2020-07-03T23:20:37+00:00 urn:sha1:653c0912628382388ceb8a3cf29e88dad35b98ac This adds `read_exact_at` and `write_all_at` to WASI's `FileExt`, similar to the Unix versions of the same names. 2020-07-07T19:35:26+00:00 bors bors@rust-lang.org 2020-07-07T19:35:26+00:00 urn:sha1:8ac1525e091d3db28e67adcbbd6db1e1deaa37fb libstd: remove some mutable statics in sys::unix My understanding is that this achieves the same behavior and performance with safe code. 2020-07-07T00:45:32+00:00 Manish Goregaokar manishsmail@gmail.com 2020-07-07T00:45:32+00:00 urn:sha1:86f8c5350f172efd5fb98d83c4fb51900fd4abe6 Fix the return type of Windows' `OpenOptionsExt::security_qos_flags`. This adjusts the return type of Windows' `OpenOptionsExt::security_qos_flags` to be consistent with the other functions in the trait. 2020-07-07T00:45:15+00:00 Manish Goregaokar manishsmail@gmail.com 2020-07-07T00:45:15+00:00 urn:sha1:218d96ed6b7d57bd5d8c38f649a22b8d4ac31c25 [rustdoc] Page hash handling Fixes https://github.com/rust-lang/rust/issues/70476 A good example to see the change is to use this URL: https://doc.rust-lang.org/nightly/std/string/struct.String.html#from_iter.v-3 After the change, it actually goes to the target element (and change the page hash to something more clear for the users). r? @kinnison cc @ollie27 2020-07-07T00:13:54+00:00 Andy Russell arussell123@gmail.com 2020-07-03T18:13:22+00:00 urn:sha1:792f2dedd7d910d35f91f32aa222b05d91cb0c65 2020-07-05T23:04:27+00:00 Dan Gohman sunfish@mozilla.com 2020-07-03T19:05:59+00:00 urn:sha1:6196eaa0b1ca4e7857d8d62817aebf3b03216a57 This adjusts the return type of Windows' `OpenOptionsExt::security_qos_flags` to be consistent with the other functions in the trait. 2020-07-02T11:19:04+00:00 Guillaume Gomez guillaume1.gomez@gmail.com 2020-06-27T22:43:01+00:00 urn:sha1:af2962027721b8dc700de339350f96b284c15fcd 2020-07-01T14:42:48+00:00 Manish Goregaokar manishsmail@gmail.com 2020-07-01T14:42:48+00:00 urn:sha1:3951a98ec5a53e527f0b2d1791b3db31738a107a Remap Windows ERROR_INVALID_PARAMETER to ErrorKind::InvalidInput from Other I don't know if this is acceptable or how likely it is to break existing code, but it seem to me ERROR_INVALID_PARAMETER "The parameter is incorrect" should map to ErrorKind::InvalidInput "A parameter was incorrect". Previously this value fell through to ErrorKind::Other. I can't speak for anyone but myself, but I instinctively thought it would be InvalidInput.