GitHub PushEvent at 2014-07-07 05:00:09
Repository: rust
Actor: Heather
Payload: {"shas":[["1fefa5b5149211c7acd11fd2ab78d9ca9873ed92","60c6d277a8bd81de7fdde19201bf9c58a3df08f4@alexcrichton.com","Updated release notes for 0.11.0","Alex Crichton",true],["d2ff9d804aa0281adc6a8733467616db9cc2fe22","60c6d277a8bd81de7fdde19201bf9c58a3df08f4@alexcrichton.com","Update AUTHORS.txt","Alex Crichton",true],["aa1163b92de7717eb7c5eba002b4012e0574a7fe","60c6d277a8bd81de7fdde19201bf9c58a3df08f4@alexcrichton.com","Update to 0.11.0","Alex Crichton",true],["e11503f6d2b1766a852183f5591874ec53f6eae5","0e9d9283f1e2e7101413c9b37446e5bea98c5425@csclub.uwaterloo.ca","librustc: Allow coercions through arrays.","Luqman Aden",true],["8284ef63a517690a893ffda1083fb966a76b6fbc","fa90a1997d4882d213aab2a4993e89213953b222@gmail.com","std: make sure HashMap from_iter uses random initialization by default\n\nIt turns out that HashMap's from_iter implementation was being\ninitialized without the sip keys being randomized. This adds\na custom default hasher that should avoid this potential vulnerability.","Erick Tryzelaar",true],["c1ff089c275592044057841673256ec78d6c400c","fa90a1997d4882d213aab2a4993e89213953b222@gmail.com","std: micro optimize Hash{Map,Set}::{new,with_capacity}","Erick Tryzelaar",true],["8dff029f9d155ca9dbc317d362919e5e43c2a232","60c6d277a8bd81de7fdde19201bf9c58a3df08f4@alexcrichton.com","Updated release notes for 0.11.0","Alex Crichton",true],["d90b71cff68ec3748b9f42063513773da57e01e2","fa90a1997d4882d213aab2a4993e89213953b222@gmail.com","std: move the hash docstring over to std::hash.","Erick Tryzelaar",true],["8b272238f1d10c9f0a77010f0a998cd697722748","0f090b00e1f6f00c3ad93f3af1e80f8d76cac273@mimiga.net","test: Add tests for issue #12223, \"drop allowed while active borrows\nstill in scope\".\n\nThis issue was fixed by PR #12828 and #5781. All that was left was to\nadd tests.\n\nCloses #12223.","Patrick Walton",true],["454b9d2d1f742d25f95b956649a9a6d92b522da4","0f090b00e1f6f00c3ad93f3af1e80f8d76cac273@mimiga.net","librustc: Fix `expr_use_visitor` (and, transitively, the borrow check)\nwith overloaded calls.\n\nThis enforces the mutability and borrow restrictions around overloaded\ncalls.\n\nCloses #14774.\n\n[breaking-change]","Patrick Walton",true],["dfdce47988b7d98c617254904f8c62d1f4d83824","c49462fef669560e618607913e6c283f7627123c@gmail.com","Rename recvfrom -> recv_from, sendto -> send_to.\n\nPOSIX has recvfrom(2) and sendto(2), but their name seem not to be\nsuitable with Rust. We already renamed getpeername(2) and\ngetsockname(2), so I think it makes sense.\n\nAlternatively, `receive_from` would be fine. However, we have `.recv()`\nso I chose `recv_from`.\n\nSigned-off-by: OGINO Masanori <masanori.ogino@gmail.com>","OGINO Masanori",true],["55f5a1ef59849709a012fcd7e2f89e7ccc42b159","c49462fef669560e618607913e6c283f7627123c@gmail.com","Add `recvfrom` and `sendto`.\n\nWe leave them for compatibility, but mark them as deprecated.\n\nSigned-off-by: OGINO Masanori <masanori.ogino@gmail.com>","OGINO Masanori",true],["f89cc11827a36e6d1eb4e22322a51eb9b1153450","19e794c1bad8f0914a9eb04e9876660727aa8f3b@gmail.com","rustdoc: s/nil/unit/ internally.\n\nQuick poll on IRC suggested that unit was the preferred name for ().","Huon Wilson",true],["d21336ee0a3982bdc35f17cdc32b41f6de5603d4","a6cc2cef7d25f27847876bdb81651755fcebacf0@mozilla.com","rustc: Remove `&str` indexing from the language.\n\nBeing able to index into the bytes of a string encourages\npoor UTF-8 hygiene. To get a view of `&[u8]` from either\na `String` or `&str` slice, use the `as_bytes()` method.\n\nCloses #12710.\n\n[breaking-change]","Brian Anderson",true],["9af1b0e5e1a0f3efb3773ae857e280cb9d099afe","60c6d277a8bd81de7fdde19201bf9c58a3df08f4@alexcrichton.com","travis: Move from travis_wait to time-passes\n\nIt's looking like we're still timing out all over the place with travis_wait\nbecause the entire `make -j4 rustc-stage1` command is taking too long. Instead,\nachieve roughly the same idea by just having `-Z time-passes` printing\ninformation. We shouldn't have a pass that takes longer than 10 minutes in\nisolation.","Alex Crichton",true],["bd893d19223ae6979c180291be6b2a3b9311148a","3a2c29237f73c7cf88424b80e427b1884f346b35@rust-lang.org","auto merge of #15069 : luqmana/rust/cia, r=pcwalton\n\nFixes #11205.","bors",true],["e56dbad9f7c3691bcb12edfaeda5cb3b660496de","0f090b00e1f6f00c3ad93f3af1e80f8d76cac273@mimiga.net","librustc: Properly compare implementation method type parameter bounds\nwith the corresponding trait parameter bounds.\n\nThis is a version of the patch in PR #12611 by Florian Hahn, modified to\naddress Niko's feedback.\n\nIt does not address the issue of duplicate type parameter bounds, nor\ndoes it address the issue of implementation-defined methods that contain\n*fewer* bounds than the trait, because Niko's review indicates that this\nshould not be necessary (and indeed I believe it is not). A test has\nbeen added to ensure that this works.\n\nThis will break code like:\n\n    trait Foo {\n        fn bar<T:Baz>();\n    }\n\n    impl Foo for Boo {\n        fn bar<T:Baz + Quux>() { ... }\n        //             ^~~~ ERROR\n    }\n\nThis will be rejected because the implementation requires *more* bounds\nthan the trait. It can be fixed by either adding the missing bound to\nthe trait:\n\n    trait Foo {\n        fn bar<T:Baz + Quux>();\n        //             ^~~~\n    }\n\n    impl Foo for Boo {\n        fn bar<T:Baz + Quux>() { ... }  // OK\n    }\n\nOr by removing the bound from the impl:\n\n    trait Foo {\n        fn bar<T:Baz>();\n    }\n\n    impl Foo for Boo {\n        fn bar<T:Baz>() { ... }  // OK\n        //       ^ remove Quux\n    }\n\nThis patch imports the relevant tests from #2687, as well as the test\ncase in #5886, which is fixed as well by this patch.\n\nCloses #2687.\nCloses #5886.\n\n[breaking-change]","Patrick Walton",true],["89259b34c04aff7052dd122552fac3070c830f4f","3a2c29237f73c7cf88424b80e427b1884f346b35@rust-lang.org","auto merge of #15085 : brson/rust/stridx, r=alexcrichton\n\nBeing able to index into the bytes of a string encourages\r\npoor UTF-8 hygiene. To get a view of `&[u8]` from either\r\na `String` or `&str` slice, use the `as_bytes()` method.\r\n\r\nCloses #12710.\r\n\r\n[breaking-change]\r\n\r\nIf the diffstat is any indication this shouldn't have a huge impact but it will have some. Most changes in the `str` and `path` module. A lot of the existing usages were in tests where ascii is expected. There are a number of other legit uses where the characters are known to be ascii.","bors",true],["7c4d8e94ba58713c65f125f721e0d95f7f66c035","3a2c29237f73c7cf88424b80e427b1884f346b35@rust-lang.org","auto merge of #15257 : erickt/rust/hashmap, r=alexcrichton\n\nWhile `HashMap::new` and `HashMap::with_capacity` were being initialized with a random `SipHasher`, it turns out that `HashMap::from_iter` was just using the default instance of `SipHasher`, which wasn't randomized. This closes that bug, and also inlines some important methods.","bors",true],["c85d42a3054e2859aac67b143485f6cd8a0693e9","47207a6890ade34efd755d6d630f1c4e984fc02d@sector5d.org","Fix example in docs on documentation","Derecho",true]],"size":182,"ref":"refs/heads/master","head":"d9db7f6137122c1cf174518cc402e04d54c3c8c3"}