Carification needed : Defining functions from rust and avoiding expensinve clones
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 32
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I am using Rhai as a scripting language for a small project of mine which involve expensive to clone/large structures.
As I would love to avoid cloning and Rhai does not support references except for the first parameter, I am unsure about the correct course of actions.
It is mentioned but it might be good to add some examples, clarifications and/or best practices around this issue.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named; start by locating the existing Rhai Book material about defining functions from Rust and avoiding expensive clones. Done means adding examples, clarifications, or best practices that explain how to work with large structures and references in this situation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100