Closed benluddy closed 7 months ago
Thoughts?
Sounds great. I had been thinking to myself, "what if a user needs to distinguish between ill-formed input and well-formed input that is rejected by the application's protocol." Now I realize that that case can be served just fine by a second call to Wellformed
using a permissive decode mode on error cases.
I'll implement your recommendations today.
I'll implement your recommendations today.
Done. Please take another look when you have a chance.
D'oh! Thank you. Added test cases to catch that and fixed.
Description
Implements #512 to allow users to error rather than encode or decode NaN and Inf floating-point values.
PR Was Proposed and Welcomed in Currently Open Issue
Checklist (for code PR only, ignore for docs PR)
Last line of each commit message should be in this format:
Signed-off-by: Firstname Lastname firstname.lastname@example.com
Certify the Developer's Certificate of Origin 1.1