https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=try 2020-07-28T00:51:13+00:00 2020-07-28T00:51:13+00:00 mark markm@cs.wisc.edu 2020-06-12T02:31:49+00:00 urn:sha1:2c31b45ae878b821975c4ebd94cc1e49f6073fd0 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-04-14T13:29:39+00:00 Youngsuk Kim joseph942010@gmail.com 2020-04-14T13:29:39+00:00 urn:sha1:de143312f8c7c137f09418878045a48331463d19 2019-12-25T15:35:54+00:00 Lzu Tao taolzu@gmail.com 2019-12-25T15:35:54+00:00 urn:sha1:3a2ef17194d7bfe56e75a3504327b38bcad979ef see accouncement at https://docs.microsoft.com/welcome-to-docs 2019-12-21T11:16:18+00:00 Ross MacArthur ross@macarthur.io 2019-12-21T11:16:18+00:00 urn:sha1:f7256d28d1c2f8340ab5b99df4bdb15aa232f3f3 2019-11-30T02:37:58+00:00 David Tolnay dtolnay@gmail.com 2019-11-27T18:28:39+00:00 urn:sha1:c34fbfaad38cf5829ef5cfe780dc9d58480adeaa This commit applies rustfmt with rust-lang/rust's default settings to files in src/libstd/sys *that are not involved in any currently open PR* to minimize merge conflicts. THe list of files involved in open PRs was determined by querying GitHub's GraphQL API with this script: https://gist.github.com/dtolnay/aa9c34993dc051a4f344d1b10e4487e8 With the list of files from the script in outstanding_files, the relevant commands were: $ find src/libstd/sys -name '*.rs' \ | xargs rustfmt --edition=2018 --unstable-features --skip-children $ rg libstd/sys outstanding_files | xargs git checkout -- Repeating this process several months apart should get us coverage of most of the rest of the files. To confirm no funny business: $ git checkout $THIS_COMMIT^ $ git show --pretty= --name-only $THIS_COMMIT \ | xargs rustfmt --edition=2018 --unstable-features --skip-children $ git diff $THIS_COMMIT # there should be no difference 2019-07-26T14:35:59+00:00 Alex Crichton alex@alexcrichton.com 2019-07-25T16:44:04+00:00 urn:sha1:c69f367bafb3a2f90d44fe54fc20d57996fa294a This commit adds accessors for more fields in `fs::Metadata` on Windows which weren't previously exposed. There's two sources of `fs::Metadata` on Windows currently, one from `DirEntry` and one from a file itself. These two sources of information don't actually have the same set of fields exposed in their stat information, however. To handle this the platform-specific accessors of Windows-specific information all return `Option` to return `None` in the case a metadata comes from a `DirEntry`, but they're guaranteed to return `Some` if it comes from a file itself. This is motivated by some changes in CraneStation/wasi-common#42, and I'm curious how others feel about this platform-specific functionality! 2019-03-31T10:56:51+00:00 Mazdak Farrokhzad twingoow@gmail.com 2019-03-01T08:34:11+00:00 urn:sha1:379c380a60e7b3adb6c6f595222cbfa2d9160a20 2019-03-29T04:07:09+00:00 Andy Russell arussell123@gmail.com 2019-03-29T00:45:40+00:00 urn:sha1:e995fa8aeaa4bfe92d270ddb9e1dd8b5516eaa25 2019-03-02T13:16:12+00:00 bors bors@rust-lang.org 2019-03-02T13:16:12+00:00 urn:sha1:fab272e5ef92b5f0b4f10c1b42c7dbcb5cec0f78 Set secure flags when opening a named pipe on Windows Fixes https://github.com/rust-lang/rust/issues/42036, see also the previous attempt in https://github.com/rust-lang/rust/pull/44556. Whether this is correct depends on if it is somehow possible to create a symlink to a named pipe, outside the named pipe filesystem (NPFS). But as far as I can tell that should be impossible. Also fixes that `security_qos_flags(SECURITY_ANONYMOUS)` does not set the `SECURITY_SQOS_PRESENT` flag, and the incorrect documentation about the default value of `security_qos_flags`.