Improved Formatted Reading#23
Merged
brightprogrammer merged 1 commit intomasterfrom Sep 2, 2025
Merged
Conversation
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
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.
Formatted reading now better detects the length of content to be parsed. Before attempting to read value at a placeholder, it'll first find the maximum possible length of reading that. This works by the following logic :
{} {}, first placeholder can only read up until first space. Then rest becomes possible read length of second placeholder.This new logic makes fmt reading much more helpful and easy to work with. This means more string format checking when parsing input. Pair this with the new format specifier
{s}in last PR #22, it makes it easier to parse strings, and formatted strings!