nice, my code can parse leap-seconds.list and verify the checksum and many other sorts of cromulence
and print out a new version of leap-seconds.list, and re-parse it, and get the same answer
1
2
bah
conflicting implementations of trait `std::convert::TryFrom<&str>` for type `std::vec::Vec<leapsecs::LeapSec>`:
1
1
hmm and i canβt impl FromStr either because Vec<LeapSec> isnβt defined in my crate even though LeapSec _is_ defined in my crate
1
1
yeah i think iβll just wrap the vec in a tuple struct because iβll want to define a bunch of other methods on it
1
2
std::convert::TryFrom has an associated type called Error
and std::str::FromStr has an associated type called Err
π¦oopsπ¦
1
2
hmm, i have both a binary and library target in this crate, and cargo runs all the tests for each target, so it runs the tests twice
canβt see if thereβs a cfg attribute for targets so i can disable them in the source
tho i can turn off the lib tests in cargo.toml
2
2
Yes, that's basically #include'ing the tests over again.
You *should* be using the lib crate as any other client application would. In what way were you having trouble before?
May 4, 2021 Β· 6:40 PM UTC
1

