-
Notifications
You must be signed in to change notification settings - Fork 184
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
Better modularisation in icu_provider
#5088
Conversation
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.
Not convinced this makes things better; I understand the desire to reduce re-exports but then why not make the modules more private? At least the macros are convenient to have on the top level since they are usually called in a chain, whereas the other types can be imported.
ffi/capi/src/provider.rs
Outdated
#[allow(unused_imports)] // feature-specific | ||
use icu_provider::MaybeSendSync; | ||
use icu_provider::any::MaybeSendSync; |
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: This trait isn't really any
related and should probably be in a different module
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.
It's only used for bounds in this module, so the only usages outside this module are AnyPayloadProvider
and one tutorial that uses any.
This PR namesspaces all macros in
icu_provider
, and exports every type only under a single path (as well as the prelude).