Repository navigation
Support loading all integer, float, and char types - #36
Merged
Merged
Conversation
CarlOlsson
approved these changes
Aug 24, 2026
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.
Implemented scalar loading improvements on
tucker/integers.Changes in PortableStructs.jl:
Realvalues can convert to any concreteIntegertarget.Realvalues can convert to anyAbstractFloattarget.Charloading now explicitly converts the single decoded character to the requested character type.kwargs...semicolon in the old integer method.Coverage includes signed and unsigned widths,
Int128,UInt128,BigInt,Bool,Float16,Float32,Float64,BigFloat, and UnicodeChar. The complete test suite passes.One existing serialization limitation remains: very large signed
Int128/BigIntnumeric scalars can exceed YAML.jl’sInt64parser, andBigFloatoutput may lose precision throughFloat64. Quoted integer strings load correctly; serialization behavior was left unchanged as requested.