feat: add native parsing for xsd:float #94
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.
Summary
Implement native parsing support for xsd:float.
Refactor the parsing logic to use a switch-case structure for better readability and maintainability, replacing the previous if-else chain. Integer and double cases are now handled separately, allowing the use of the most suitable standard library parsing methods. This change also eliminates the use of fmt.Sprintf for float-to-integer checks, improving performance.
Basic example
The n-quads
should be converted to the following when using native types:
[ { "@id": "http://example.com/Subj1", "http://example.com/prop": [ { "@value": 0.11 } ] } ]Motivation
Consistent behavior. It is counterintuitive that
doubleis converted to a native value whilefloatis not. (Unfortunately,xsd:decimalmust not be converted, as required by Test t0018.)Checks
make test