I’m getting this error, which I totally believe Rust is having a problem with, but it is a bit frustrating to try and figure out what it is having a hard time with. It seems to blow some internal limit on depth, probably in some sort of recursive trait evaluation, but it won’t print the stack (that I can discover) so I can’t really tell where it thinks the cycle is.
I have a repo at https://github.com/frankmcsherry/trie/, which should explode with
cargo build. The likely culprit is trying to evaluate whether the result of
Sized or not, which … well I think all of the types are well-founded at the call site, and it shouldn’t be a big deal, but I’m guessing Rust has either found some other possible implementations, or has a wonky evaluation strategy that explores too deeply in some direction. I’m not sure, but any advice would be great!