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

EnC: allow moving type to another file #50876

Closed
tmat opened this issue Jan 28, 2021 · 0 comments
Closed

EnC: allow moving type to another file #50876

tmat opened this issue Jan 28, 2021 · 0 comments
Milestone

Comments

@tmat
Copy link
Member

tmat commented Jan 28, 2021

Version Used:
Version 16.9.0 Preview 4.0 [30920.304.main]

Steps to Reproduce:

Moving a type declaration (top-level or nested) to another file is currently a rude edit. We can allow the change by recompiling all the type's members with bodies so that the PDB records are updated. Similarly we should allow deleting a partial class definition as long as all the members it contained are moved to another part of the partial class.

Related: #51399

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Interactive untriaged Issues and PRs which have not yet been triaged by a lead labels Jan 28, 2021
@tmat tmat added Interactive-EnC and removed Area-Interactive untriaged Issues and PRs which have not yet been triaged by a lead labels Jan 28, 2021
@tmat tmat added this to the Backlog milestone Jan 28, 2021
@tmat tmat closed this as completed Feb 23, 2021
@tmat tmat modified the milestones: Backlog, 16.10 Feb 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant