Chris

Moving this to 0.7.0 because that version will change the format of stuff in the ASN.1 encoding, so it's a good time to handle this. _Edit:_ der 0.8 has not...

Running this code in `0.14.0` returns a quaternion of (0, 0, 0, 1). ``` Finished dev [unoptimized + debuginfo] target(s) in 0.55 secs Running `target/debug/mybin` Some( Unit { value: Quaternion...

Yes, that's a good idea. I don't know how to solve this. Maybe it could be a crate feature which toggles either the vendored ssl or not? Do you have...

Would it be possible to have the vendored feature enabled by default and then add another feature for native (if that's the opposite of vendored?) that also enables openssl but...

Related to #280

Hi there, Rest assured, the time computations are validated and match SPICE. However, you've likely found the exact reason why I've had an issue implementing #294 ! I tried to...

It looks like the Python build requires the vendor feature.

Hi there, What output are you expecting? At first glance, this looks correct to me because you're calling the to_utc_seconds which accounts for leap seconds when initializing T1.

I believe the leap second happens at the TAI time, not at the UTC time. From [data.iana.org/time-zones/data/leap-seconds.list](https://data.iana.org/time-zones/data/leap-seconds.list): > UTC differs from TAI by an integer number of seconds; it is...

You've convinced me that hifitime applies the leap second too early. The original IERS file, a copy of which can be found [here](https://github.com/eggert/tz/blob/4e604e41115182c3ab1185bab4c888822511348e/leap-seconds.list), state this: > The first column shows...