Statically-compilable ISO lowers for Date, DateTime, and Time - #476
Merged
Conversation
…Time Temporal values lowered through the generic StringLike path — string(x) — which routes into the Dates format machinery: rpad/repeat padding and type-info printing are dynamic, so writing any Date/DateTime/Time field failed juliac --trim=safe verification. The trim workload had no temporal field, which is how it slipped through. Emit exactly string(x) through fixed-format printers instead: signed wide years, DateTime's fraction omitted at zero milliseconds and three digits otherwise, and Time's tiered subsecond field with trailing zeros stripped. Parity is fuzz-tested against string(x) across all field combinations, and the trim workload now round-trips a temporal struct (reads require StructUtils 2.8.4, pinned in the trim test project). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #476 +/- ##
==========================================
- Coverage 90.49% 89.98% -0.51%
==========================================
Files 7 7
Lines 1452 1518 +66
==========================================
+ Hits 1314 1366 +52
- Misses 138 152 +14 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
quinnj
added a commit
to quinnj/juliacon-2026-workshop
that referenced
this pull request
Aug 10, 2026
The native build now rides four upstream fixes instead of app-side serialization code. JSON writes Date/DateTime/Time through fixed-format ISO printers (JuliaIO/JSON.jl#476) and StructUtils hand-parses ISO 8601 in its temporal lifts, accepting RFC 3339 offsets on DateTime normalized to UTC (JuliaServices/StructUtils.jl#68) — both pinned until released. Registered HTTP 2.6.2 and JuliaC 0.3.8 trim-verify clean, so those pins and the trim_strict_bodies preference go away entirely. What remains native-specific is structural, not serialization: the webhook endpoint is not registered (the image runs no event runtime), and the stored-summary disk mirror still flattens one nesting level — typed parsing of doubly-nested shapes awaits JuliaLang/julia#62661. juliac --trim=safe verifies with zero errors; the 62MB from-scratch container serves the generated typed client end to end. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
quinnj
added a commit
to quinnj/juliacon-2026-workshop
that referenced
this pull request
Aug 10, 2026
The native build now rides four upstream fixes instead of app-side serialization code. JSON writes Date/DateTime/Time through fixed-format ISO printers (JuliaIO/JSON.jl#476) and StructUtils hand-parses ISO 8601 in its temporal lifts, accepting RFC 3339 offsets on DateTime normalized to UTC (JuliaServices/StructUtils.jl#68) — both pinned until released. Registered HTTP 2.6.2 and JuliaC 0.3.8 trim-verify clean, so those pins and the trim_strict_bodies preference go away entirely. What remains native-specific is structural, not serialization: the webhook endpoint is not registered (the image runs no event runtime), and the stored-summary disk mirror still flattens one nesting level — typed parsing of doubly-nested shapes awaits JuliaLang/julia#62661. juliac --trim=safe verifies with zero errors; the 62MB from-scratch container serves the generated typed client end to end. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
quinnj
added a commit
to quinnj/juliacon-2026-workshop
that referenced
this pull request
Aug 10, 2026
The native build now rides four upstream fixes instead of app-side serialization code. JSON writes Date/DateTime/Time through fixed-format ISO printers (JuliaIO/JSON.jl#476) and StructUtils hand-parses ISO 8601 in its temporal lifts, accepting RFC 3339 offsets on DateTime normalized to UTC (JuliaServices/StructUtils.jl#68) — both pinned until released. Registered HTTP 2.6.2 and JuliaC 0.3.8 trim-verify clean, so those pins and the trim_strict_bodies preference go away entirely. What remains native-specific is structural, not serialization: the webhook endpoint is not registered (the image runs no event runtime), and the stored-summary disk mirror still flattens one nesting level — typed parsing of doubly-nested shapes awaits JuliaLang/julia#62661. juliac --trim=safe verifies with zero errors; the 62MB from-scratch container serves the generated typed client end to end. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Temporal values lowered through the generic
StringLikepath —string(x)— which routes into the Dates format machinery:rpad/repeatpadding and type-info printing are dynamic, so writing anyDate/DateTime/Timefield failedjuliac --trim=safeverification. The trim workload had no temporal field, which is how it slipped through.This emits exactly
string(x)through fixed-format printers instead:Date: signed, ≥4-digit years ("-0001-01-01","12345-01-01")DateTime: fraction omitted at zero milliseconds, always three digits otherwise ("…T00:00:00","…T00:00:00.010")Time: tiered subsecond field (ms/µs/ns) with trailing zeros stripped ("01:02:03.01"), matchingprint(::IO, ::Time)Parity is fuzz-tested against
string(x)across 60k random values plus the edge tiers, and the trim workload now round-trips a temporal struct.Ordering: the workload's typed reads need the matching lift fix in JuliaServices/StructUtils.jl#68; this PR's trim test project pins
StructUtils = \"2.8.4\", so that PR wants to land and release first.Found while updating the JuliaCon workshop app to the registered stack (a 62MB from-scratch native image now builds clean against these two fixes with no app-side serialization workarounds).
🤖 Generated with Claude Code