bors fff484d18e Auto merge of #11977 - y21:is_const_evaluatable_ice, r=Manishearth ... don't visit nested bodies in `is_const_evaluatable` Fixes #11939 This ICE happened in `if_let_some_else_none`, but the root problem is in one of the utils that it uses. It is (was) possible for `is_const_evalutable` to visit nested bodies which would lead to it trying to get the type of one of the expressions with the wrong typeck table, which won't have the type stored. Notably, for the expression `Bytes::from_static(&[0; 256 * 1024]);` in the linked issue, the array length is an anonymous const in which type checking happens on its own, so we can't use the typeck table of the enclosing function in there. Visiting nested bodies is also not needed for checking whether an expression can be const, so I think it's safe to ignore just ignore them altogether. changelog: Fix ICE when checking for constness in nested bodies		2023-12-16 22:54:50 +00:00
..
src	Auto merge of #11977 - y21:is_const_evaluatable_ice, r=Manishearth	2023-12-16 22:54:50 +00:00
Cargo.toml	Update itertools to 0.11.	2023-11-22 08:13:21 +11:00