JP Sugarbroad
JP Sugarbroad
+1 to this. I'm handling old mainframe datasets, and there's a bit that says whether the structures are big-endian or little-endian. This is what I have: ```rust struct WrapOrder {...
I expect a minimal version of the program. If these features are actually required for the binary, then there should be a `required-features` declaration: https://doc.rust-lang.org/cargo/reference/cargo-targets.html#the-required-features-field
(It is also common to have a feature "cli" or similar that enables only the minimal required features for the binary, which is often a subset of the default features.)
I'm confused. If you didn't want to "split up the program into multiple features" then why are there optional dependencies?
Perhaps that could properly be handled by a flag somewhere in that build? `--no-deps` perhaps?
As far as I can tell from debugging, the weird string values are coming from Xero's JSON data.
Aha, documented: http://developer.xero.com/documentation/advanced-docs/dates-and-timestamps-explained/
Well, I'm trying to set the date of a payment to the due date of an invoice.
Thankfully there appears to be a DateString I can use in the mean time, but it's not quite the same.
FWIW, +1 to a readFully method on BYOB readers. Maybe a new issue for it?