@@ -129,9 +129,9 @@ fn naively_apply_time_zone_name(
129
129
/// * `length_patterns` - Contains information on how to combine date and time patterns.
130
130
/// * `fields` - The desired fields to match against.
131
131
/// * `prefer_matched_pattern` - This algorithm does some extra steps of trying to respect
132
- /// the desired fields, even if the provider data doesn't completely match. This
133
- /// configuration option makes it so that the final pattern won't have additional work
134
- /// done to mutate it to match the fields. It will prefer the actual matched pattern.
132
+ /// the desired fields, even if the provider data doesn't completely match. This
133
+ /// configuration option makes it so that the final pattern won't have additional work
134
+ /// done to mutate it to match the fields. It will prefer the actual matched pattern.
135
135
pub fn create_best_pattern_for_fields < ' data > (
136
136
skeletons : & DateSkeletonPatterns < ' data > ,
137
137
length_patterns : & GenericLengthPatterns < ' data > ,
@@ -375,9 +375,9 @@ fn apply_subseconds(pattern: &mut runtime::Pattern, subseconds: Option<Subsecond
375
375
/// * Compute a score based on the best possible match for the given fields.
376
376
/// * Select the skeleton with highest score.
377
377
/// * Modify the resulting pattern to have fields of the same length. For example requesting
378
- /// a skeleton "yMMMMd" can have a best match of ["yMMMd", "d MMM y"]. This pattern should
379
- /// then be modified to use the requested length to produce a pattern "d MMMM y".
380
- /// However, fields should not be changed from numeric to text.
378
+ /// a skeleton "yMMMMd" can have a best match of ["yMMMd", "d MMM y"]. This pattern should
379
+ /// then be modified to use the requested length to produce a pattern "d MMMM y".
380
+ /// However, fields should not be changed from numeric to text.
381
381
///
382
382
/// The following is not implemented:
383
383
///
0 commit comments