Skip to content
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

Document recommendations for using crates that have std types in public interface #101

Open
FeldrinH opened this issue Jan 30, 2023 · 0 comments

Comments

@FeldrinH
Copy link

FeldrinH commented Jan 30, 2023

Perhaps I've missed an important part of the documentation, but it seems to me that using this crate with other crates that use std types in public api involves a lot of copying.

For example if I have a crate that manipulates Vec-s from the standard library and I then want to make those Vec-s accessible over ABI then I have no option other than to make a copy to RVec, which could be really bad for performance if the Vec-s are large.

Is this assessment accurate? Are the tradeoffs and recommendations for these kinds of situations documented somewhere? If not it would be useful if they were.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant