https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.26.2 2018-03-28T22:18:13+00:00 2018-03-28T22:18:13+00:00 bors bors@rust-lang.org 2018-03-28T22:18:13+00:00 urn:sha1:d52c44ea8df9f9045e6059cb2d37df743be50bb1 Rollup of 12 pull requests - Successful merges: #49243, #49329, #49364, #49400, #49405, #49427, #49428, #49429, #49439, #49442, #49444, #49452 - Failed merges: 2018-03-28T18:11:44+00:00 bors bors@rust-lang.org 2018-03-28T18:11:44+00:00 urn:sha1:e5277c1457d397f22ba18a1d40c1318729becbb4 Remove hidden `foo` functions from doc examples; use `Termination` trait. Fixes https://github.com/rust-lang/rust/issues/49233. Easier to review with the white-space ignoring `?w=1` feature: https://github.com/rust-lang/rust/pull/49357/files?w=1 2018-03-28T11:15:05+00:00 Corey Farwell coreyf@rwell.org 2018-03-25T02:56:07+00:00 urn:sha1:e9dcec070d6097e5a22b6658844dccd9d1f578cf Fixes https://github.com/rust-lang/rust/issues/49233. 2018-03-27T00:39:11+00:00 Diggory Blake diggsey@googlemail.com 2018-03-26T22:24:31+00:00 urn:sha1:04f6692aaf78809c041ba6145bde2dcbeec9725e 2018-03-21T16:54:33+00:00 Simon Sapin simon.sapin@exyr.org 2018-03-17T11:15:24+00:00 urn:sha1:c09b9f937250db0f51b705a3110f8cffdad083bb The trait and some of its methods are stable and will remain. Some of the newer methods are unstable and can be removed later. Fixes https://github.com/rust-lang/rust/issues/39658 2018-03-04T02:44:44+00:00 Scott McMurray scottmcm@users.noreply.github.com 2018-03-04T02:29:30+00:00 urn:sha1:74c5c6e6cb0425284f57fece6fbf248e827ea06d Now begins the saga of fixing compilation errors on other platforms... 2018-02-17T11:32:16+00:00 bors bors@rust-lang.org 2018-02-17T11:32:16+00:00 urn:sha1:b298607864b76ea6b7b7a4b8bb482472f1604c8d This is the ideal FileType on Windows. You may not like it, but this is what peak performance looks like. Theoretically this would fix https://github.com/rust-lang/rust/issues/46484 The current iteration of this PR should not cause existing code to break, but instead merely improves handling around reparse points. Specifically... * Reparse points are considered to be symbolic links if they have the name surrogate bit set. Name surrogates are reparse points that effectively act like symbolic links, redirecting you to a different directory/file. By checking for this bit instead of specific tags, we become much more general in our handling of reparse points, including those added by third parties. * If something is a reparse point but does not have the name surrogate bit set, then we ignore the fact that it is a reparse point because it is actually a file or directory directly there, despite having additional handling by drivers due to the reparse point. * For everything which is not a symbolic link (including non-surrogate reparse points) we report whether it is a directory or a file based on the presence of the directory attribute bit. * Notably this still preserves invariant that when `is_symlink` returns `true`, both `is_dir` and `is_file` will return `false`. The potential for breakage was far too high. * Adds an unstable `FileTypeExt` to allow users to determine whether a symbolic link is a directory or a file, since `FileType` by design is incapable of reporting this information. 2018-02-11T18:40:46+00:00 Peter Atashian retep998@gmail.com 2018-02-11T18:40:46+00:00 urn:sha1:9269e83b37e8e5fd9cef12255fafbc6db6220035 2018-02-03T06:52:04+00:00 Peter Atashian retep998@gmail.com 2018-02-03T06:52:04+00:00 urn:sha1:c42d76d3c80b4938e26e628706363b677fde6ca1 Unflip it 2018-02-03T06:45:58+00:00 Peter Atashian retep998@gmail.com 2018-02-03T06:45:58+00:00 urn:sha1:f4c83693f9e2445b441dfcf43838697d25d1a11f Be smarter about what a symlink is however