-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
Bad generic inference on very recent nightly #105037
Copy link
Copy link
Closed
Labels
A-const-genericsArea: const generics (parameters and arguments)Area: const generics (parameters and arguments)C-bugCategory: This is a bug.Category: This is a bug.F-generic_const_exprs`#![feature(generic_const_exprs)]``#![feature(generic_const_exprs)]`
Metadata
Metadata
Assignees
Labels
A-const-genericsArea: const generics (parameters and arguments)Area: const generics (parameters and arguments)C-bugCategory: This is a bug.Category: This is a bug.F-generic_const_exprs`#![feature(generic_const_exprs)]``#![feature(generic_const_exprs)]`
Type
Fields
Give feedbackNo fields configured for issues without a type.
We noticed a build error in Plonky2 on the nightly build 2022-11-27. The same code was building last week, on a slightly older nightly.
Here's a minimal reproducible example (Playground):
Nightly 2022-11-27 gives this error:
It seems to be sensitive to the order of the where clauses,
[(); Table1::<D>::COLUMNS]:and[(); Table2::<D>::COLUMNS]:. I.e. for aprocess_tablecall, it seems to infer thatTis whicheverTableappeared last in thewherelist.