New week, new Rust! What are you folks up to?
using mir for silly things, and writing the typetoken crate.
I've published version 0.2.1 of my little image-comparison library rendiff, which is intended for testing the output of renderers. The big new features, since the original 0.1.0 release, are that the visual diff output is now much more legible (in both highlighting differences and marking their position), and that it no longer depends on the image library (which means that it doesn't need updating when image has a breaking release). It also has much more documentation and example code.
These days, I think that, when designing a library, it's very important to keep public dependencies (that is, those whose types/traits appear in the library’s API surface) minimal. Not for compile times, not for download sizes, but to keep churn low. In general, if foo 1.0 publicly depends on bar 1.0, then when bar releases 2.0, foo likely must too, and dependents of both must wait for both releases to occur and possibly release their own, and so on. But if foo doesn't publicly depend on bar — whether or not it depends on bar internally — then there is no such cascade, and foo's dependents are insulated from bar's choices.
3 Likes
This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.