-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add concat_slice
and mark everything as unsafe
#7
Conversation
Chooses the very cautious option of erroring in all cases of a ZST concatentation.
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.
What do you think about combining concat
and concat_slice
like this? I think it would make the usage more intuitive.
Adding a trait to the interface that can not be implemented seems to complicate the interface (it requires an additional indirection to find the valid uses). I'd either rename the methods to
|
See issue oberien#7, we must guarantee that slices are from the same allocation. However, pointer equality testing can not reliably test this so it must be provided by the caller. Some actual safe interface is coming back at some point, currently the proof obligation is still highly reduced.
See issue oberien#7, we must guarantee that slices are from the same allocation. However, pointer equality testing can not reliably test this so it must be provided by the caller. Some actual safe interface is coming back at some point, currently the proof obligation is still highly reduced.
concat_slice
concat_slice
and mark everything as unsafe
Could you please also add an example of |
Chooses the very cautious option of erroring in all cases of a ZST
concatentation for now.