{"push_id":694897980,"size":2,"distinct_size":0,"ref":"refs/heads/master","head":"e89bb24cb267dfa1bf9acee6a06b3221114ae7f5","before":"cc44423566726260e316d879a0a1dd9d3fb92e07","commits":[{"sha":"bddb685e7322c8ffb9578ae9e5a3a161071b257b","author":{"email":"a2efa2b758ab72066c3f54752ab11d60ffc4331f@gmail.com","name":"petrochenkov"},"message":"Use `assert_eq!` instead of `assert!` in tests","distinct":false,"url":"https://api.github.com/repos/rust-lang/rust/commits/bddb685e7322c8ffb9578ae9e5a3a161071b257b"},{"sha":"e89bb24cb267dfa1bf9acee6a06b3221114ae7f5","author":{"email":"3a2c29237f73c7cf88424b80e427b1884f346b35@rust-lang.org","name":"bors"},"message":"Auto merge of #26071 - petrochenkov:assert1, r=alexcrichton\n\n`assert_eq!` has better diagnostics than `assert!` and is more helpful when something actually breaks, but the diagnostics has it's price - `assert_eq!` generate some formatting code which is slower to compile and possibly run.\r\n[My measurements](https://internals.rust-lang.org/t/assert-a-b-or-assert-eq-a-b/1367/12?u=petrochenkov) show that presence of this formatting code doesn't affect compilation + execution time of the test suite significantly, so `assert_eq!` can be used instead of `assert!` consistently.\r\n\r\n(Some tests doesn't reside in src/test, they are not affected by these changes, I'll probably open a separate PR for them later)","distinct":false,"url":"https://api.github.com/repos/rust-lang/rust/commits/e89bb24cb267dfa1bf9acee6a06b3221114ae7f5"}]}