Skip to content
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 EitherProvider and rename IterableDataProviderCore to IterableProvider #1455

Merged
merged 4 commits into from
Dec 31, 2021

Conversation

sffc
Copy link
Member

@sffc sffc commented Dec 30, 2021

This also moves KeyedDataProvider into the CLDR crate since it has limited use outside of the core crate and I'd like to replace it with something better (see #442).

@sffc sffc marked this pull request as ready for review December 30, 2021 23:00
@sffc sffc requested review from nordzilla and a team as code owners December 30, 2021 23:00
/// .or_else(|err| DataProviderB::or_else_supports_key(err, resc_key))
/// .or_else(|err| DataProviderC::or_else_supports_key(err, resc_key))
/// ```
fn or_else_supports_key(err: DataError, resc_key: &ResourceKey) -> Result<(), DataError> {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: i'd call this chainable_supports_key() or something, the or_else makes it feel like it's doing something else, whereas it really means that it's supposed to be used inside or_else.

(i know this is an existing naming choice, but i just noticed it. feel free to ignore)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sffc sffc merged commit 7d9f89f into unicode-org:main Dec 31, 2021
@sffc sffc deleted the iterprov branch December 31, 2021 02:02
@sffc sffc removed the request for review from nordzilla December 31, 2021 02:03
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.

None yet

2 participants