|
4 | 4 |
|
5 | 5 | use crate::fallback::LocaleFallbackConfig; |
6 | 6 | use crate::{DataError, DataErrorKind, DataLocale, DataProvider, DataProviderWithMarker}; |
| 7 | +use core::fmt; |
7 | 8 | use core::marker::PhantomData; |
8 | 9 | use yoke::Yokeable; |
9 | 10 | use zerovec::ule::*; |
@@ -506,7 +507,7 @@ impl DataMarkerPath { |
506 | 507 | /// Executables can be searched for `DataMarkerInfo` instances to produce optimized data files. |
507 | 508 | /// Therefore, users should not generally create DataMarkerInfo instances; they should instead use |
508 | 509 | /// the ones exported by a component. |
509 | | -#[derive(Debug, Copy, Clone, PartialEq, Eq)] |
| 510 | +#[derive(Copy, Clone, PartialEq, Eq)] |
510 | 511 | #[non_exhaustive] |
511 | 512 | pub struct DataMarkerInfo { |
512 | 513 | /// The human-readable path string ends with `@` followed by one or more digits (the version |
@@ -622,6 +623,12 @@ macro_rules! __data_marker_path { |
622 | 623 | #[doc(inline)] |
623 | 624 | pub use __data_marker_path as data_marker_path; |
624 | 625 |
|
| 626 | +impl fmt::Debug for DataMarkerInfo { |
| 627 | + fn fmt(&self, f: &mut fmt::Formatter) -> fmt::Result { |
| 628 | + self.path.fmt(f) |
| 629 | + } |
| 630 | +} |
| 631 | + |
625 | 632 | /// A marker for the given `DataStruct`. |
626 | 633 | #[derive(Clone, Copy, PartialEq, Eq, Hash, Debug)] |
627 | 634 | pub struct ErasedMarker<DataStruct: for<'a> Yokeable<'a>>(PhantomData<DataStruct>); |
|
0 commit comments