You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is literaly no const eval in const generics yet, so Const<{ four }> is Const<_>. We can handle this special case easily, but the constants in nalgebra are very complex and evaluating them needs trait resolution (#4558) + lowering const generics to body (#7434) + evaluating assoc consts with generic parameters. Short term solution here IMO is replace type u4 = Const<{ typenum::U4::USIZE }> with type U4 = Const<4> in the nalgebra source code, which is an internal and invisible to user change.
Would this be a reasonable change to make? Rust analyzer has a lot of trouble with nalgebra's types, and this is a big impediment to using the crate in beginner settings. Arguably this is a problem that rust analyzer should solve, but if a simple fix like this helps it seems worthwhile.
The text was updated successfully, but these errors were encountered:
From rust-lang/rust-analyzer#11803 (comment) :
Would this be a reasonable change to make? Rust analyzer has a lot of trouble with nalgebra's types, and this is a big impediment to using the crate in beginner settings. Arguably this is a problem that rust analyzer should solve, but if a simple fix like this helps it seems worthwhile.
The text was updated successfully, but these errors were encountered: