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

[Meta Discussion] Moving Language Design issues out of this repo #18002

Closed
gafter opened this Issue Mar 20, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@gafter
Member

gafter commented Mar 20, 2017

We are now taking language feature discussion in other repositories:

Features that are under active design or development, or which are "championed" by someone on the language design team, have already been moved either as issues or as checked-in design documents. For example, the proposal in this repo "Proposal: Partial interface implementation a.k.a. Traits" (and a few other issues that request the same thing) are now tracked by the language team at dotnet/csharplang#52, and there is a draft spec at https://github.com/dotnet/csharplang/blob/master/proposals/default-interface-methods.md and further discussion at dotnet/csharplang#288 . Prototyping of the compiler portion of language features is still tracked here; see, for example, https://github.com/dotnet/roslyn/tree/features/DefaultInterfaceImplementation and #17952 .

In order to facilitate that transition, we have started closing the least recently active language design discussions from the roslyn repo with a note briefly explaining why. When we are aware of an existing discussion for the feature already in the new repo, we are adding a link to that. But we're not adding new issues to the new repos for existing discussions in this repo that the language design team does not currently envision taking on. Our intent is to eventually close the language design issues in the Roslyn repo and encourage discussion in one of the new repos instead.

Our intent is not to shut down discussion on language design - you can still continue discussion on the closed issues if you want - but rather we would like to encourage people to move discussion to where we are more likely to be paying attention (the new repo), or to abandon discussions that are no longer of interest to you.

If you happen to notice that one of the closed issues has a relevant issue in the new repo, and we have not added a link to the new issue, we would appreciate you providing a link from the old to the new discussion. That way people who are still interested in the discussion can start paying attention to the new issue.

Also, we'd welcome any ideas you might have on how we could better manage the transition.

@gafter gafter self-assigned this Mar 20, 2017

This was referenced Mar 20, 2017

@jcouv

This comment has been minimized.

Member

jcouv commented Dec 15, 2017

@gafter I'll close this issue now.
There are some stranded language design issues in the roslyn repo that we can still move as we encounter them.

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