Skip to content

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

@FeldrinH

Description

@FeldrinH

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions