Skip to content

fix: ensure TO_STRING conversion functions do not panic (1.0.x) - #1905

Open
ghaith wants to merge 1 commit into
rusty-backport-4659from
rusty-backport-4692
Open

fix: ensure TO_STRING conversion functions do not panic (1.0.x)#1905
ghaith wants to merge 1 commit into
rusty-backport-4659from
rusty-backport-4692

Conversation

@ghaith

@ghaith ghaith commented Sep 2, 2026

Copy link
Copy Markdown
Collaborator

Problem: The *_TO_STRING conversions cover only a few widths, format the short date and time types without their literal prefixes, and can panic on unexpected input or overflow their result buffers.

Solution: Move the TO_STRING and STRING_TO declarations into dedicated standard library files, add the missing BOOL, integer and bit-string conversions with well defined result lengths, and format date and time values with their literal prefixes through one panic-free writer. Lengths are sized for the 64-bit nanosecond types used on this release line.

Backport of #1903. Depends on #1904.

Refs: PRG-4692

🤖 Generated with Claude Code

Problem: The *_TO_STRING conversions cover only a few widths, format the
short date and time types without their literal prefixes, and can panic
on unexpected input or overflow their result buffers.

Solution: Move the TO_STRING and STRING_TO declarations into dedicated
standard library files, add the missing BOOL, integer and bit-string
conversions with well defined result lengths, and format date and time
values with their literal prefixes through one panic-free writer. Lengths
are sized for the 64-bit nanosecond types used on this release line.

Backport of #1903.

Refs: PRG-4692

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant