Abstract members are not correctly filtered out of available options for further processors
Bug #692440 reported by
Philip Peitsch
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NGineer |
New
|
Undecided
|
Unassigned |
Bug Description
Abstract members appear to trip up NGineer, appearing as available when they will not actually be writable. Demonstration hierarchy is as follows:
public class ParentClass
{
public abstract string Property { get; }
}
public class ChildClass : ParentClass
{
public string Property { get { return "Hello"; } }
}
Update: this seems to be triggered directly by the IgnoreAll() method
description: | updated |
To post a comment you must log in.