Use `core`'s `AssertParamIsClone` and `AssertParamIsCopy` traits
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 231
- Avg merge
- 19h 55m
- Merged PRs (30d)
- 67
Description
These traits are used to produce better errors when expanding derive(Clone) macros, but they are not lang items. Hence we cannot refer to them using a lang-item path, and instead need to use a full-blown core path (::core::clone::AssertParamIsCopy). This is problematic for us as we cannot yet compile or distribute core, and thus we do not always link user code to it.
Once we have figured out how to distribute core, we'll be able to make use of these assertions.
Contributor guide
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 files, tests, or entry points are named. Start by reviewing how gccrs distributes or links core and how derive(Clone) expansion currently references AssertParamIsClone and AssertParamIsCopy; done means those assertions can be used without relying on the full core path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100