-
Notifications
You must be signed in to change notification settings - Fork 47
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
Analyzer to suggest using readonly struct
#603
Comments
Hi @SteveDunn . I wanted to take this issue, if that's alright |
That would be great, thank you! |
Should |
Hi, yes I think so. The benefits apply to them too. 👍
…On Sun, 18 Aug 2024, 16:09 danigutsch, ***@***.***> wrote:
Should record structs trigger the analyzer?
—
Reply to this email directly, view it on GitHub
<#603 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACAJ6DHH6M7AJHAIAW7QRDZSC2JFAVCNFSM6AAAAABIJXJXGOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJVGI4TIMBYGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It is preferable for users to use a
readonly struct
rather than just astruct
. Implement an analyzer to suggest this, and possibly a codefix.This was a result of the following thread.
Originally posted by @Herdo in #52 (comment)
The text was updated successfully, but these errors were encountered: