-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ICE with const generics with disabled feature flag #69913
Comments
Source: fn foo<const A: usize, const B: usize>(bar: [usize; A + B]) {
//
} Godbolt shows that the ICE occurs in 1.39.0 and not in 1.38.0. cargo bisect-rustc indicates that the regression is in nightly-2019-08-21. We're outside of the 167 day CI date range window to bisect at the commit level with the tool. Here is the commit dump: commit[0] 2019-08-19UTC: Auto merge of #63579 - alexcrichton:new-lockfile, r=Mark-Simulacrum |
@rustbot claim |
will be fixed by lazy normalization. |
…lcnr,estebank Fix missing diagnostic span for `impl Trait` with const generics, and add various tests for `min_const_generics` and `const_generics` Closes rust-lang#61410. Adds `min_const_generics` tests for: - rust-lang#73727 - rust-lang#72293 - rust-lang#67375 - rust-lang#75153 - rust-lang#71922 - rust-lang#69913 - rust-lang#67945 - rust-lang#69239 Adds `const_generics` tests for: - rust-lang#67375 - rust-lang#75153 - rust-lang#71922 - rust-lang#69913 - rust-lang#67945 - rust-lang#69239 (I only added separate `min_const_generics` and `const_generics` tests if they were handled differently by the two features.) We need to figure out how to deduplicate when `const_generics` is stabilised, but we can discuss that later. For now, we should be checking neither feature breaks, so require regression tests for both. I've given them identical names when I've added both, which should make it easier to spot them later. r? @lcnr
Triage: |
we already have a bunch of similar tests, closing without adding an an additional one |
Hi,
Following code ICEs on stable (1.41.1), beta (1.42.0-beta.6) and nightly (2020-03-10):
(playground)
The issue arises when:
[usize; A + B]
in this case),Backtrace
The text was updated successfully, but these errors were encountered: