-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TOML SerializationFormat
fails for GdsLibrary
#33
Comments
Rooting around /// # Gds Date & Time
///
/// In typical cases, a wrapper around a [`NaiveDateTime`] with custom serialization.
/// For existing GDSII files with invalid dates, the raw twelve bytes are stored instead.
///
#[derive(Clone, Debug, Deserialize, Serialize, JsonSchema, PartialEq)]
pub enum GdsDateTime {
/// Valid Date & Time
DateTime(NaiveDateTime),
/// Raw Bytes as stored in GDSII
Bytes([i16; 6]),
} |
Bet lost. Errors have upgraded to:
We've got an open question with the |
SerialzationFormat
fails for GdsLibrary
SerializationFormat
fails for GdsLibrary
toml-rs/toml#396 was recently closed, and updated in TOML v0.6.
This is hitting TOML's Much of the guesswork (by me) thus far on the TOML issue is that this boils down to TOML's "values must come before tables" rule. It seems (from its commentary) that the Rust TOML package should paper over this. But then again maybe not. |
This:
Fails with:
Notes:
lef21::LefLibrary
Unclear at this point what the
UnsupportedType
is.Unclear when this was injected, as we had generally only been testing one format of serialization (GDS to JSON, LEF to YAML, nothing to TOML). And it wasn't clear that there are value-types supported in YAML & JSON that aren't in TOML(?). Apparently
GdsLibrary
has one or more of them.The text was updated successfully, but these errors were encountered: