Hey #rustlang, I've been jumping into big crates lately to try to "figure out how things work".
I usually read http://docs.rs , then check out the source and play around with it, but this is pretty ad-hoc. Do ya'll have tips for your "grok a new crate" workflow?
-
Show this thread
-
Replying to @does_he_byte
If a crate has tests, I often look at some of those right after the documentation. (Not the "corner case" tests, but the "correct behavior" tests.) And if a crate has other crates depending on it, I'll look at a couple of its high-profile users for large-scale examples.
2 replies 0 retweets 7 likes
Replying to @josh_triplett
This also has some risk depending on how old the crate is. The first thing I wrote at all for Diesel was a test, and tests from those days haven't really been touched unless they stopped compiling, meaning they don't look anything like what I'd expect real code to look like
5:45 PM - 3 May 2020
0 replies
0 retweets
2 likes
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.