Handle arbitrary self types

Open
  • Is something wrong?
#4,838 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
cpp, rust
Domain
compilers

Research direction

Start with the Rust unstable-book description of arbitrary self types linked in the issue. Map the feature's impact across the compiler, especially typechecking and method probing, before defining a focused milestone or smaller task. Done should include support for arbitrary self types, but the issue does not specify tests or a narrower completion boundary.

Written by the indexing model from the issue text.

Description

codegen name resolution parser rust-for-linux typechecking

https://doc.rust-lang.org/unstable-book/language-features/arbitrary-self-types.html

This is probably going to be very annoying as it touches maaaaaany areas of the compiler including typechecking and method probing. This is used by the kernel. This might be worth splitting into its own entire milestone

Dominant language
C++
Stars
3k
Forks
238
Avg merge
4d 8h
Merged PRs (30d)
31

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Rust-GCC/gccrs

All issues in Rust-GCC/gccrs

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.