Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tracking issue for the Traits Working Group #48416

Open
nikomatsakis opened this Issue Feb 22, 2018 · 10 comments

Comments

Projects
None yet
8 participants
@nikomatsakis
Copy link
Contributor

nikomatsakis commented Feb 22, 2018

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.

@lloydmeta

This comment has been minimized.

Copy link
Member

lloydmeta commented Feb 22, 2018

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

@giannicic

This comment has been minimized.

Copy link
Contributor

giannicic commented Feb 22, 2018

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.

@JoeyEremondi

This comment has been minimized.

Copy link

JoeyEremondi commented Feb 22, 2018

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.

@autodidaddict

This comment has been minimized.

Copy link

autodidaddict commented Feb 22, 2018

Interested in contributing however ICan.

@Centril

This comment has been minimized.

Copy link
Contributor

Centril commented Feb 22, 2018

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 =)

@nikomatsakis

This comment has been minimized.

Copy link
Contributor Author

nikomatsakis commented Feb 23, 2018

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.

@GeertVL

This comment has been minimized.

Copy link

GeertVL commented Feb 23, 2018

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

@nikomatsakis

This comment has been minimized.

Copy link
Contributor Author

nikomatsakis commented Feb 28, 2018

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!

@nikomatsakis

This comment has been minimized.

Copy link
Contributor Author

nikomatsakis commented Oct 5, 2018

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.

@dhardy

This comment has been minimized.

Copy link
Contributor

dhardy commented Oct 8, 2018

By my reckoning the meeting should be now?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.