-
-
Notifications
You must be signed in to change notification settings - Fork 703
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add 'std.format.read.formattedRead' overloads to return a Tuple with values read #8647
Merged
LightBender
merged 4 commits into
dlang:master
from
iK4tsu:feat-formattedRead-tuple-return
Nov 26, 2024
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
7bcb86b
refactor(formattedRead): add not is type validation to template argum…
iK4tsu 1e68278
feat(formattedRead): add overloads to return a tuple with the read va…
iK4tsu e068a9e
test(formattedRead): add unnittests for the tuple return type overloads
iK4tsu 38520d1
chore(changelog): add a changelog formattedRead entry
iK4tsu File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
Extend the functionality of formattedRead to permit a std.file.slurp like execution. | ||
|
||
Template argument types can now be passed to formattedRead along with a | ||
format string to parse and read the input range as a Tuple of those arguments. | ||
All arguments must be read successfully, otherwise, and unlike std.file.slurp | ||
which has non exhaustive option for partial reads, it'll throw a std.format.FormatException. | ||
|
||
--- | ||
import std.exception : assertThrown; | ||
import std.format : FormatException; | ||
import std.typecons : tuple; | ||
|
||
@safe pure unittest | ||
{ | ||
auto complete = "hello!34.5:124".formattedRead!(string, double, int)("%s!%s:%s"); | ||
assert(complete == tuple("hello", 34.5, 124)); | ||
|
||
assertThrown!FormatException("hello!34.5:".formattedRead!(string, double, int)("%s!%s:%s")); | ||
} | ||
|
||
/// The format string can be checked at compile-time: | ||
@safe pure unittest | ||
{ | ||
auto expected = tuple("hello", 124, 34.5); | ||
auto result = "hello!124:34.5".formattedRead!("%s!%s:%s", string, int, double); | ||
assert(result == expected); | ||
|
||
assertThrown!FormatException("hello!34.5:".formattedRead!("%s!%s:%s", string, double, int)); | ||
} | ||
--- |
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the format string can be checked at compile-time, why would one need to pass in types?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The format string is not responsible for unformatting into the types the user wants, it's only to know the places in the input string that need to be unformatted and to tell the formatted the restrictions of the characters it's reading. Using
%f
can still be valid for bothfloat
anddouble
for example, and it asserts statically when the types are not format-compatible.It also asserts on orphan format specifiers or if the number of arguments is higher than the required by the format string. This is useful for generic code when we don't have total control over the argument quantity or the format string. The format string might be generated during compile time causing it to assert if some malformation occurs, or the variadic template arguments might be calculated at compile time asserting for the same reasons.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I actually think I found a bug in
checkFormatException
for the%f
format.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please file a bug report for this?