{"push_id":633825685,"size":82,"distinct_size":82,"ref":"refs/heads/deprecate_unicode_fns","head":"9952769c1ad6061ff9def79b718ba8a1f25fc0b9","before":"516795d9a2f122325a2f9bf34e20f529a61b016a","commits":[{"sha":"1a28237b4240f267a465e5179decbfdd7a26bf47","author":{"email":"16aea3ed30350b1f4b4dfc1111a05a38e3d681b3@rwell.org","name":"Corey Farwell"},"message":"Alter libcore::result example to utilize closure param\n\nSince it doesn't utilize the parameter, it's not very idiomatic since it\ncould just use the `Result::or` method. So this changes the example to\nutilize the parameter. As far as I can tell, all the numbers in this\nexample are completely arbitrary.","distinct":true,"url":"https://api.github.com/repos/kwantam/rust/commits/1a28237b4240f267a465e5179decbfdd7a26bf47"},{"sha":"734bdc656a6fae7a2c1f5722de4c1f9611bc28b5","author":{"email":"9ce5770b3bb4b2a1d59be2d97e34379cd192299f@steveklabnik.com","name":"Steve Klabnik"},"message":"copyedits: functions","distinct":true,"url":"https://api.github.com/repos/kwantam/rust/commits/734bdc656a6fae7a2c1f5722de4c1f9611bc28b5"},{"sha":"2b38819b8409cbadc74260c3beb7559f6515155e","author":{"email":"9ce5770b3bb4b2a1d59be2d97e34379cd192299f@steveklabnik.com","name":"Steve Klabnik"},"message":"copyedits: documentation","distinct":true,"url":"https://api.github.com/repos/kwantam/rust/commits/2b38819b8409cbadc74260c3beb7559f6515155e"},{"sha":"f1515fabb027e901a5cb47826f12ba89db2df078","author":{"email":"b1db332606efda9d9987ee09ce352e2a96143e72@gmail.com","name":"Guillaume Gomez"},"message":"Add Default trait for AtomicBool, AtomicIsize and AtomicUsize","distinct":true,"url":"https://api.github.com/repos/kwantam/rust/commits/f1515fabb027e901a5cb47826f12ba89db2df078"},{"sha":"f329030b095aa30ce29be0c3459615d85506747b","author":{"email":"60c6d277a8bd81de7fdde19201bf9c58a3df08f4@alexcrichton.com","name":"Alex Crichton"},"message":"std: Stabilize the Utf8Error type\n\nThe meaning of each variant of this enum was somewhat ambiguous and it's uncler\nthat we wouldn't even want to add more enumeration values in the future. As a\nresult this error has been altered to instead become an opaque structure.\nLearning about the \"first invalid byte index\" is still an unstable feature, but\nthe type itself is now stable.","distinct":true,"url":"https://api.github.com/repos/kwantam/rust/commits/f329030b095aa30ce29be0c3459615d85506747b"},{"sha":"912a872d3c7e12a5d9784c3bfd4cd3c911e468d9","author":{"email":"b38e964bedaa3ccf271853eb16eef0311461431c@gmail.com","name":"Theo Belaire"},"message":"Fixed with_extension documentation bug\n\nIt was mistakenly calling it with \"foo.txt\" instead of \"txt\".\nI've also added an assert.","distinct":true,"url":"https://api.github.com/repos/kwantam/rust/commits/912a872d3c7e12a5d9784c3bfd4cd3c911e468d9"},{"sha":"12d21bf99c1341d273ffcf0cbf4ba8c5d1d42a12","author":{"email":"1f81e848faf55004077c594fb2256b536cb2c8e0@gmail.com","name":"Theo Belaire"},"message":"References to `CString::from_vec` changed to `new`\n\nIt looks like `from_vec` was subsumed by new at some point,\nbut the documentation still refers to it as `from_vec`.\n\nThis updates the documentation for `from_vec_unchecked`\nso that it properly says that it's the unchecked version of `new`.\n\nAlso, from_vec_unchecked requires a actual Vec<u8> while\nnew can take anything that is Into<Vec<u8>>, so I also\nmention that in the documentation.","distinct":true,"url":"https://api.github.com/repos/kwantam/rust/commits/12d21bf99c1341d273ffcf0cbf4ba8c5d1d42a12"},{"sha":"219f61bdd89cab251884d0645c07916343231b59","author":{"email":"c078c0ddeac7b7a4d2b7ec5268a0d9ae4c662761@gmail.com","name":"Robin Kruppe"},"message":"Make Debug include the - in -0.0","distinct":true,"url":"https://api.github.com/repos/kwantam/rust/commits/219f61bdd89cab251884d0645c07916343231b59"},{"sha":"cef96b95f210b225b49ab172074f32938e2046db","author":{"email":"12c875436a19b99bf0b96f0110d54611e83c2b9b@barosl.com","name":"Barosl Lee"},"message":"rustdoc: Prevent '/' from showing the help dialog\n\nOnly '?' should do that.\n\nFixes #24289.","distinct":true,"url":"https://api.github.com/repos/kwantam/rust/commits/cef96b95f210b225b49ab172074f32938e2046db"},{"sha":"c3c83bfda486c430514a3a008423f2c536c4bcc9","author":{"email":"1d6e1cf70ec6f9ab28d3ea4b27a49a77654d370e@kgv.name","name":"kgv"},"message":"Arity link has moved to primitive-types.md.","distinct":true,"url":"https://api.github.com/repos/kwantam/rust/commits/c3c83bfda486c430514a3a008423f2c536c4bcc9"},{"sha":"e891f29b95bb45ad3ce642b4387a977fae547939","author":{"email":"d5e0892e7d66bcce47406a02632e7b4f50cda414@gmail.com","name":"Björn Steinbrink"},"message":"Fix ICE when returning a variable whose declaration is unreachable\n\nFixes #24353","distinct":true,"url":"https://api.github.com/repos/kwantam/rust/commits/e891f29b95bb45ad3ce642b4387a977fae547939"},{"sha":"6f54ce9aa5d2baf0cd82c01e2c181ab17439b7d7","author":{"email":"fdc34241055c362abd04c9402a0cf27e42d4db6b@gmail.com","name":"pez"},"message":"added _SC_NPROCESSORS_ONLN constants for linux and macos for fix #24374","distinct":true,"url":"https://api.github.com/repos/kwantam/rust/commits/6f54ce9aa5d2baf0cd82c01e2c181ab17439b7d7"},{"sha":"883bb6568d2b5659de197cea612656f757fc22af","author":{"email":"fdc34241055c362abd04c9402a0cf27e42d4db6b@gmail.com","name":"pez"},"message":"remove duplicated linux sysconf mod","distinct":true,"url":"https://api.github.com/repos/kwantam/rust/commits/883bb6568d2b5659de197cea612656f757fc22af"},{"sha":"39543e91f51eead5a00242e7eda6a0fced06ceea","author":{"email":"d8304a100f9eb6d8398a1b27f47b5aa4c1c0b0be@gmail.com","name":"Ariel Ben-Yehuda"},"message":"Don't try to suggest fields of an enum\n\nFixes #24365","distinct":true,"url":"https://api.github.com/repos/kwantam/rust/commits/39543e91f51eead5a00242e7eda6a0fced06ceea"},{"sha":"951db77267c649083374784810257dbcdb9cb941","author":{"email":"fa90a1997d4882d213aab2a4993e89213953b222@gmail.com","name":"Erick Tryzelaar"},"message":"syntax: Publically expose printing where clauses, and add attr_to_string","distinct":true,"url":"https://api.github.com/repos/kwantam/rust/commits/951db77267c649083374784810257dbcdb9cb941"},{"sha":"6fa16d6a473415415cb87a1fe6754aace32cbb1c","author":{"email":"06a7813f879e3069b8b80d175ff4f9d3508d9379@gmail.com","name":"Andrew Paseltiner"},"message":"pluralize doc comment verbs and add missing periods","distinct":true,"url":"https://api.github.com/repos/kwantam/rust/commits/6fa16d6a473415415cb87a1fe6754aace32cbb1c"},{"sha":"6399bb425b3a82111cd554737f194c95b8f6bad5","author":{"email":"9df59a69f337cdc0a275d7c2f347281b851067f9@mozilla.com","name":"Aaron Turon"},"message":"De-stabilize `thread::scoped` and friends\n\nIssue #24292 demonstrates that the `scoped` API as currently offered can\nbe memory-unsafe: the `JoinGuard` can be moved into a context that will\nfail to execute destructors prior to the stack frame being popped (for\nexample, by creating an `Rc` cycle).\n\nThis commit reverts the APIs to `unstable` status while a long-term\nsolution is worked out.\n\n(There are several possible ways to address this issue; it's not a\nfundamental problem with the `scoped` idea, but rather an indication\nthat Rust doesn't currently provide a good way to ensure that\ndestructors are run within a particular stack frame.)\n\n[breaking-change]","distinct":true,"url":"https://api.github.com/repos/kwantam/rust/commits/6399bb425b3a82111cd554737f194c95b8f6bad5"},{"sha":"f60f4b7d7cde90edb248159cf5e351816cce8d8a","author":{"email":"0731fdeb307910eeaae4e58897b7baaba45e054b@cloudscaling.com","name":"Abhishek Chanda"},"message":"Fix check for globally routable IPv4 address\n\n- Adds two more functions for broadcast address and special\n  address classes reserved for documentation\n- Modifies the globally routable IP check to include these\n  new functions\n\nFixes #24314","distinct":true,"url":"https://api.github.com/repos/kwantam/rust/commits/f60f4b7d7cde90edb248159cf5e351816cce8d8a"},{"sha":"32f7e673c8e095c79940882d23a3258a48150185","author":{"email":"46f1a0bd5592a2f9244ca321b129902a06b53e03@kazlauskas.me","name":"Simonas Kazlauskas"},"message":"Refine read_to_end documentation","distinct":true,"url":"https://api.github.com/repos/kwantam/rust/commits/32f7e673c8e095c79940882d23a3258a48150185"},{"sha":"6e0fb70ff6effe7b7be2c5fe951e9161613e6707","author":{"email":"9df59a69f337cdc0a275d7c2f347281b851067f9@mozilla.com","name":"Aaron Turon"},"message":"Generalize `spawn` beyond unit closures\n\n`thread::spawn` was previously restricted to closures that return `()`,\nwhich limited the utility of joining on a spawned thread. However, there\nis no reason for this restriction, and this commit allows arbitrary\nreturn types.\n\nSince it introduces a type parameter to `JoinHandle`, it's technically\na:\n\n[breaking-change]\n\nHowever, no code is actually expected to break.","distinct":true,"url":"https://api.github.com/repos/kwantam/rust/commits/6e0fb70ff6effe7b7be2c5fe951e9161613e6707"}]}