Let trait Fill be implemented for element types
#1652
+74
−94
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
These impls contradict the doc that fn fill is implemented for types which may be reinterpreted as [u8].
newpavlov
approved these changes
Aug 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
CHANGELOG.mdentrySummary
This is a simpler variant (no specialization support) of #1651.
Fillimpls to types safely reinterpretable as a byte-slice. This removes additional capability gained in Replace AsByteSliceMut with Fill #940.Fillto the element type, not slice/array. This supports external impls on externally-defined types. Fixes CHANGE: AllowFillto be implemented for third-party types #1650.Motivation
This trait was added to fill a capability gap: a safe interface for fast filling of slices like
[i16]. The impls for[bool],[f32]etc. are extra complexity beyond this and unnecessary since they offer no benefit over element-wise generation in user-code.