I was initially skeptical about Rust's convention of having tests in the same file as the actual code, but it seems to be working out well.
-
-
It's difficult enough to keep compatibility across versions when you're programming against a public API. With tests, you often want to check internals.
-
Oh, you wouldn't, but the fact it's hard at the moment is sort of the point: If the tests aren't in sync with your main repo, then some of them would just fail (at compile time). You would update them if/when you care enough to do so, but no requirement for it to be synchronous.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.