-
Notifications
You must be signed in to change notification settings - Fork 184
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
Remove type fallback from datagen #6115
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A bit annoying that you need to check extra data structs to get the name you need, but the size win is compelling.
I can follow the fallback chain when it is illustrated.
Seems likely that bugs will arise with all this fallbacking; make sure it is well tested.
MetazoneGenericStandardNamesLongV1, | ||
"time_zone/generic_standard_long@1", | ||
has_checksum |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestion: Maybe name it metazone/standard/names/long/v1
(on the same level as generic and standard)?
Falling back from the
generic
to thestandard
display name for the generic format in datagen means thestandard
display name will be included in both generic and specific data structs.This introduces a second "generic standard" data struct that contains generic names that are actually standard. This data struct is used by both the generic and the specific format.