3 ms·
> All problems they're facing are due to the decision to make tests a "special case" rather than just normal Rust code that happens to test things. That's one
by the_mitsuhiko 3y ago
> All problems they're facing are due to the decision to make tests a "special case" rather than just normal Rust code that happens to test things.
That's one way in which this can be interpreted, but I don't really agree. I think the problems are a classic case of a "good enough" solution that shipped very early and became core of the ecosystem. Now it's hard to move off it or to improve it as it's in a case of stasis.
Even today you do not need to use `#[test]` or the built-in functionality at all. (The exception being that the internals of the print interception are not exposed, but there are other ways around that).
Fundamentally the frustration of the state is not high enough, and nobody pushes strongly for a much improved testing solution. But technology wise, you would not need anything from the language to have a better test system in Rust.
- golergka 3y ago> the problems are a classic case of a "good enough" solution that shipped very early and became core of the ecosystem BTW, that's the exact reason I like lack of a “good standard library” in JS that people usually cite as a downside. When there's a good enough default solution it suffocates evolution of different ideas in the field.