Skip to content

tracking issue for the Traits Working Group #48416

Closed

Description

@nikomatsakis

Introduction

The Traits Working Group is dedicated to all things "trait". In particular, the goal of the working group is to create and maintain the trait engine within the Rust compiler, as well as contributors ideas and insights to the language itself, when it comes to RFCs for traits. See the announcement for more.

Key facts

How to get involved

Drop in on the Zulip channel and introduce yourself. We're just starting up again after a long hiatus, so hopefully we'll have a bit more structure once we get our footing.

Activity

  1. added
    metabugIssues about issues themselves ("bugs about bugs")
    T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.
    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
    on Feb 22, 2018
  2. lloydmeta commented on Feb 22, 2018

    @lloydmeta
    Contributor

    I only have working knowledge of traits, but I'm keen to learn more and can put some time in on a weekly basis :)

  3. giannicic commented on Feb 22, 2018

    @giannicic
    Contributor

    I'm interested in working on this. I just know the trait system at an higher level and I'd like to learn it more deeply. I'll take a look at the posts to get a general idea of the things to do.

  4. JoeyEremondi commented on Feb 22, 2018

    @JoeyEremondi

    I'm a PhD student working with Ron Garcia, extending some of Jonatan Milewski's work. I've got a research project right now where I've got a declarative model of traits in a Rust-like language, along with associated type constructors and higher-ranked types, along with a verified inference algorithm. It's almost at a point where there's a draft worth sharing.

    I'd love to be involved with this group. I've done some Rust programming, and I've got some previous experience with logic programming.

  5. autodidaddict commented on Feb 22, 2018

    @autodidaddict

    Interested in contributing however ICan.

  6. Centril commented on Feb 22, 2018

    @Centril
    Contributor

    This sounds interesting. I'd love to contribute. Thus far, I haven't done more than write RFCs and such. I haven't made any contributions to the compiler itself (outside of the standard library) yet, so I'd love to learn. Count me in =)

  7. nikomatsakis commented on Feb 23, 2018

    @nikomatsakis
    ContributorAuthor

    Hey all! Glad to hear about the interest. Sorry I didn't get to many specifics today, will try to do so tomorrow and over the weekend.

  8. GeertVL-zz commented on Feb 23, 2018

    @GeertVL-zz

    @nikomatsakis Posted it on the internals post but let you know it this way too.

  9. nikomatsakis commented on Feb 28, 2018

    @nikomatsakis
    ContributorAuthor

    cc @rust-lang/wg-traits -- I opened a thread on internals:

    First off, I want to apologize for the radio silence on this working group. It’s been harder than I anticipated to come up get a good crop of “start issues” and so forth. In general, I feel like we’re still trying to figure out the best way to get a “working group” up and going.Therefore, I thought, if I can’t figure this out on my own, why don’t we all start talking it out together? Hence this thread!

  10. nikomatsakis commented on Oct 5, 2018

    @nikomatsakis
    ContributorAuthor

    For those of you following this issue, we're trying to get this group up and going again! We plan to have a meeting (on Zulip, this time) this coming Monday.

  11. jackh726 commented on Mar 18, 2022

    @jackh726
    Member

    I'm going to go ahead and close this. wg-traits has it's own repo rust-lang/wg-traits where we can track things as needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-trait-systemArea: Trait systemC-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.metabugIssues about issues themselves ("bugs about bugs")

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions