Skip to content

Field doesn't need to be volatile #47225

@Youssef1313

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?

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