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

Fix certain solution asserts. #73195

Merged
merged 2 commits into from
Apr 23, 2024

Conversation

CyrusNajmabadi
Copy link
Member

No description provided.

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead labels Apr 23, 2024
@CyrusNajmabadi CyrusNajmabadi marked this pull request as ready for review April 23, 2024 17:18
@CyrusNajmabadi CyrusNajmabadi requested a review from a team as a code owner April 23, 2024 17:18
@@ -486,6 +486,9 @@ public static ProjectStateChecksums Deserialize(ObjectReader reader)
await ChecksumCollection.FindAsync(assetPath, state.AnalyzerConfigDocumentStates, searchingChecksumsLeft, onAssetFound, arg, cancellationToken).ConfigureAwait(false);
}
}

public override string ToString()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

public override string ToString()

Is this just for debugging purposes? If so, curious on your thoughts of doing this vs using DebuggerDisplayString

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes. i personally don't care one way or hte other. it's all internal types, so ToString seems entirely reasonable to me.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, I'm fine either way. Whenever I see a ToString, I'm never certain if it's there for debugging or for actually having it's value being used in the code.

Copy link
Contributor

@ToddGrun ToddGrun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@CyrusNajmabadi CyrusNajmabadi merged commit 8a6ff11 into dotnet:main Apr 23, 2024
25 checks passed
@CyrusNajmabadi CyrusNajmabadi deleted the solutionAsserts branch April 23, 2024 18:58
@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone Apr 23, 2024
@CyrusNajmabadi
Copy link
Member Author

@jasonmalinowski For review when you get back.

@dibarbet dibarbet modified the milestones: Next, 17.11 P1 Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants