We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is there a reason why we don't use that directly like &[u8]. Maybe an oversight when I wrote this API?
&[u8]
Then we can just return Vec<u8> than forcing wrapping.
Vec<u8>
The text was updated successfully, but these errors were encountered:
Using &[u8] or &str directly might be possible, but will require to carefully track and fix lifetime conficts.
&str
A simpler way seems to be implementing needed traits (PrimaryKey, Prefixer, probably others) directly for Vec[u8], and remove PkOwned entirely.
PrimaryKey
Prefixer
Vec[u8]
PkOwned
Sorry, something went wrong.
UniqueIndex
MultiIndex
Created #233 to track / fix the lifetimes issue.
From
Into
maurolacy
Successfully merging a pull request may close this issue.
Is there a reason why we don't use that directly like
&[u8]
. Maybe an oversight when I wrote this API?Then we can just return
Vec<u8>
than forcing wrapping.The text was updated successfully, but these errors were encountered: