Enum patternfly_yew::components::form::Wrap
source · pub enum Wrap {
Hard,
Soft,
Off,
}
Variants§
Trait Implementations§
source§impl PartialEq for Wrap
impl PartialEq for Wrap
impl Eq for Wrap
impl StructuralPartialEq for Wrap
Auto Trait Implementations§
impl Freeze for Wrap
impl RefUnwindSafe for Wrap
impl Send for Wrap
impl Sync for Wrap
impl Unpin for Wrap
impl UnwindSafe for Wrap
Blanket Implementations§
source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
source§impl<Q, K> Equivalent<K> for Q
impl<Q, K> Equivalent<K> for Q
source§impl<Q, K> Equivalent<K> for Q
impl<Q, K> Equivalent<K> for Q
source§fn equivalent(&self, key: &K) -> bool
fn equivalent(&self, key: &K) -> bool
key
and return true
if they are equal.source§impl<T> Instrument for T
impl<T> Instrument for T
source§fn instrument(self, span: Span) -> Instrumented<Self>
fn instrument(self, span: Span) -> Instrumented<Self>
source§fn in_current_span(self) -> Instrumented<Self>
fn in_current_span(self) -> Instrumented<Self>
source§impl<T> IntoPropValue<Option<T>> for T
impl<T> IntoPropValue<Option<T>> for T
source§fn into_prop_value(self) -> Option<T>
fn into_prop_value(self) -> Option<T>
self
to a value of a Properties
struct.source§impl<T> IntoPropValue<T> for T
impl<T> IntoPropValue<T> for T
source§fn into_prop_value(self) -> T
fn into_prop_value(self) -> T
self
to a value of a Properties
struct.source§impl<T> IntoTruncateContent for Twhere
T: ToString,
impl<T> IntoTruncateContent for Twhere
T: ToString,
source§fn truncate_before(self, num: usize) -> TruncateContent
fn truncate_before(self, num: usize) -> TruncateContent
This function is supposed to truncate num
characters before the end of the string.
§Bytes, Code Points, and Grapheme Clusters
However, what it actually does is to truncate the string at the next Unicode code point,
after num
bytes (not characters). This is quick and should work reasonably well with
the Latin 1 character set (or, UTF-8 characters which are represented by a single byte).
Given a string with multi-byte code points, or even grapheme clusters (user-perceived characters, which may consists of multiple Unicode code points), this will split at the wrong location.
It will still split, and not skip any data. But it might lead to an unexpected (shorter) end section.
What about an actual correct implementation? That would be possible by using an additional dependency. It would also need to count all code points and grapheme clusters from the start of the string. The question is: is that worth it? Maybe, maybe not!?