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.
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
Correct error types for
icu_provider_fs
#3682Correct error types for
icu_provider_fs
#3682Changes from all commits
6c73dbc
3565587
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Nit:
NO_PROVIDER_ERROR_KIND
orFALLBACK_ERROR_KIND
would be more clear because ForkByErrorPredicate normally uses the predicate function to test its error type.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.
Issue, here and elsewhere: using
/
is not good because Windows and other OSes need different separators. That is what PathBuf::push handles for us. I don't think eitherwrite!
orPath::new
fixes it for us sincewrite!
is writing directly to a string andPath::new
tries to borrow where possible.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.
Apparently this works because Windows tests are not failing. Note that before we used
push(&str)
, which usedAsRef<Path> for &str
, so the slashes in thestr
were still forward slashes (andpush
itself doesn't replace them).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.
Okay, so before we were appending individual path segments for root, key, and locale, but the key can contain a slash which wasn't being processed.
I wouldn't be surprised if Windows accepts these characters but does some weird handling with them.
@eggrobin and @makotokato are the two ICU4X engineers who routinely use Windows and might be able to provide some insight here.