-
Notifications
You must be signed in to change notification settings - Fork 185
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
More no-alloc #6166
base: main
Are you sure you want to change the base?
More no-alloc #6166
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.
hopefully VZCow isn't more expensive. It ought not be
@@ -130,6 +130,7 @@ struct EyepatchHackVector<U> { | |||
/// This pointer is *always* valid, the reason it is represented as a raw pointer | |||
/// is that it may logically represent an `&[T::ULE]` or the ptr,len of a `Vec<T::ULE>` | |||
buf: NonNull<[U]>, | |||
#[cfg(feature = "alloc")] |
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: explicitly document behavior when not present
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.
hm? there's no behaviour change, this is just always 0 in no-alloc
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.
I understand, however this is unsafe code, we should be doubly clear about how things change. "This field is equivalent to 0 when disabled" is fine
icu_time
,icu_decimal
,icu_list
#6076