By "programming" I don"t mean programming as in programming languages but as in "setlist", I.e. defining the progression of the curriculum (the issue title might be a clickbait but I doubt it, I"m nothing like that 😁).

Specifically, generics3.rs exercise requires knowledge about traits, and the hint even starts with the following sentence: "To find the best solution to this challenge you"re going to need to think back to your knowledge of traits, specifically Trait Bound Syntax".

But Generics module come before Traits module in current progression of exercises. I"m assuming this is some reshuffle of rustlings from earlier state where someone simply failed to notice this dependency issue.

So this should be fixed ASAP, as Rust community is supposed to care big deal about preventing data races 😁

Bad jokes aside. I do think that having generics after traits actually makes much more sense even if this wasn"t the case., as they are, much like interfaces or subtyping, a less generic (whoops) form of polymorphism than parametric polymorphism.