Skip to content

Field doesn't need to be volatileΒ #47225

Closed

Description

@Youssef1313

IDE0044 suggests the field to be readonly, which can't be used together with volatile.

It seems reasonable that volatile can be omitted. The field is only set in the constructor. How can multiple threads modify it?

Activity

  1. added
    help wantedThe issue is "up for grabs" - add a comment if you are interested in working on it
    on Sep 7, 2020
  2. added this to the Backlog milestone on Sep 7, 2020
  3. removed their assignment
    on Sep 22, 2020
  4. huoyaoyuan commented on Oct 3, 2020

    @huoyaoyuan
    Member

    Already fixed by #43542 .

  5. added
    Resolution-FixedThe bug has been fixed and/or the requested behavior has been implemented
    and removed
    help wantedThe issue is "up for grabs" - add a comment if you are interested in working on it
    on May 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area-IDEBugFeature - IDE0044Make field readonlyResolution-FixedThe bug has been fixed and/or the requested behavior has been implemented

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions