Explicit LocaleFallbacker
argument for DatagenDriver
#5114
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.
Datagen implicitly requires a
LocaleFallbacker
for most configurations, so I'd rather make it explicit so that providers that don't expose fallback themselves are exportable.I also removed the no-fallback mode, as that can (almost, up to
["und"]
) be modeled by the fallback path, and made the required settings arguments tonew
.I also added a
supported_markers
method to theExportableDataProvider
trait; datagen will by default now support all available markers for the provider. This lets me remove theall_markers
methods from the driver crate, which didn't make sense there. This allows removing theall_markers
,marker
, andmarkers
methods fromicu_datagen
, so that it's registry-agnostic.markers_for_bin
moves toicu
, as that needs theicu
crate anyway and only supports markers inicu
.