-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Replaced >= with > in condition. #14825
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
Conversation
@pavinan - is there a bug explaining what's wrong? |
@rynowak No, It just caught my eye while I am looking around for something. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Based on the comments the change seems harmless, it would be good if the PR includes a comment with a link to the appropriate documentation that states that flags.Length will always be greater than 0.
@javiercn Documentation states that if flags.Length is 0 then attribute itself is not emitted. https://github.com/dotnet/roslyn/blob/master/docs/features/nullable-metadata.md#optimizations |
@pavinan Thanks, that's the piece of data I was missing. |
@pavinan could you cherry-pick this commit to target |
@pranavkm I don't know how to do cherry-pick in GitHub. You can do it. |
Thanks for your contribution, @pavinan. |
Summary of the changes