Bug - Leading Whitespace On Stream In #53
Merged
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 is an issue where leading whitespace in an input stream buffer causes a
path
to be invalid.To reproduce:
See a compiling example here. This was tested using MSVC 16.4.5 and g++ 9.1.0. In both configurations,
std::filesystem
behaves as expected (runstd-fs
in the root directory) whereghc::filesystem
returns a path with a leading space and fails to properly parse when handed tostd::ifstream
(runalt-fs
in the root directory).The fix simply streams in the first character when testing for a quote character. This causes the operation to respect the current
skipws
flag. Usingstd::basic_istream::get()
will ignore theskipws
flag and simply read in the first character (if there is leading whitespace, a whitespace character). If theskipws
flag is set in theistream
, bothstd::filesystem
andghc::filesystem
read in the whitespace character and fail the assertion.