- 12 11月, 2015 22 次提交
-
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
This mostly brings them in line with existing linking convention, but also has some minor re-wording. The text at the top has been re-focused, by starting out with what the prelude does, rather than starting from injecting std. Also, it now mentions that other preludes exist. Part of https://github.com/rust-lang/rust/issues/29369
-
由 Manish Goregaokar 提交于
In previous PRs, I changed the match desugaring to generate more efficient code for ints/chars and the like. But this doesn't help when you're matching strings, ranges, or other crazy complex things (leading to #29740). This commit restructures match desugaring *yet again* to handle that case better -- basically we now degenerate to an if-else-if chain in such cases. ~~Note that this builds on https://github.com/rust-lang/rust/pull/29763 which will hopefully land soon. So ignore the first few commits.~~ landed now r? @Aatch since he's been reviewing the other commits in this series
-
由 bors 提交于
r? @nikomatsakis I went ahead and replaced repeat count with a `Constant`, because it cannot be non-constant to the best of my knowledge.
-
由 Niko Matsakis 提交于
bothered to track down for a regresson test. /me hopes no one notices
-
由 bors 提交于
Closes https://github.com/rust-lang/rust/issues/29746
-
由 Simonas Kazlauskas 提交于
-
由 Vadim Petrochenkov 提交于
-
由 Steve Klabnik 提交于
-
由 Steve Klabnik 提交于
This mostly brings them in line with existing linking convention, but also has some minor re-wording. The text at the top has been re-focused, by starting out with what the prelude does, rather than starting from injecting std. Also, it now mentions that other preludes exist. Part of https://github.com/rust-lang/rust/issues/29369
-
由 Niko Matsakis 提交于
large matches that fallback to Eq. When we encounter a case where the test being performed does not inform the candidate at all, we just stop testing the candidates at that point, rather than adding the candidate to both outcomes. The former behavior was not WRONG, but it generated a lot of code, whereas this new behavior degenerates to an if-else-if tree. Fixes #29740.
-
由 bors 提交于
- Successful merges: #29677, #29772, #29775, #29777 - Failed merges:
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
None
-
由 Manish Goregaokar 提交于
It's a bit strange to expect users of `libstd` to require the use of an external crates.io crate to work with standard types. This commit encourages the use `os::raw::c_char` instead, although users are certainly free to use `libc::c_char` if they wish; the test still exists to ensure the two types are identical (though the reported bug only exists on platforms that are not officially tested). Fixes #29774
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
r? @Manishearth cc @AlisdairO Part of #24407
-
由 arcnmx 提交于
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
Fixes #7526
-
由 arcnmx 提交于
-
由 bors 提交于
The older algorithm was pretty inefficient for big matches. Fixes #29227. (On my computer, MIR construction on this test case goes from 9.9s to 0.025s.) Whereas before we had a loop like: - for all outcomes of the test we are performing - for all candidates - check whether candidate is relevant to outcome We now do: - for all candidates - determine which outcomes the candidate is relevant to Since the number of outcomes in this case is proportional to the number of candidates, the original algorithm turned out to be O(n^2), and the newer one is just O(n). This PR also does some minor speedups by eagerly mirroring all patterns, so that we can just pass around `&Pattern<'tcx>`, which makes cloning cheaper. We could probably go a bit further in this direction. r? @Aatch
-
- 11 11月, 2015 18 次提交
-
-
由 Kohei Hasegawa 提交于
-
由 bors 提交于
Hi Rustaceans! This is the secong take on running latest rustfmt on librustc_driver! All fixups made in https://github.com/rust-lang/rust/pull/29033 were done (also rustfmt got better). //cc @nrc
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
`Vec` should not be resized.
-
由 bors 提交于
Moved from #29753. r? @steveklabnik
-
由 bors 提交于
None
-
由 bors 提交于
Fixes #29751.
-
由 bors 提交于
-
由 bors 提交于
Fix #16410.
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
before we iterated over the test and each outcome thereof, and then checked processed every candidate against this outcome, we now organize the walk differently. Instead, we visit each candidate and say "Here is the test being performed. Figure out the resulting candidates for each possible outcome and add yourself into the appropriate places."
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
pass around references instead of boxed values to save on clone costs.
-
由 bors 提交于
This should help avoid triggering the unused_results lint which can frequently be turned on. Closes #29710
-
由 bors 提交于
- Check privacy sanity in all blocks, not only function bodies - Check all fields, not only named - Check all impl items, not only methods - Check default impls - Move the sanity check in the beginning of privacy checking, so others could rely on it Technically it's a [breaking-change], but I expect no breakage because, well, it's *sane* privacy visitor, if code is broken it must be insane by definition!
-
由 bors 提交于
This commit adds issue numbers to the vast majority of active feature gates. The few that are left without issues are rustc/runtime-internal features that are essentially private APIs. Closes #28244 r? @huonw
-
由 Simonas Kazlauskas 提交于
-
由 bors 提交于
The comparison of IP addresses should happen not always in network endianness but rather in the host endianness format, so be sure to convert to that before comparing addresses. There are still locations where the endianness will factor into visible properties, such as the hash, but these are not important to be independent of the endianness in play (as hash values are pretty undefined anyway. Closes #29691
-