dotnet: how to handle calls/references to subsclasses and/or implementors of interfaces?
Open
Nobody has claimed this yet.
dotnet
question
- Dominant language
- Python
- Stars
- 6.2k
- Forks
- 726
- Avg merge
- 11d 11h
- Merged PRs (30d)
- 7
Description
within dotnet, objects of a concrete type may implement interfaces or be subclasses of more generic functionality. how should we extract method features in these cases? should we reference the concrete class? or the interface/superclass? or both?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the .NET method-feature extraction path, then determine how concrete classes, interfaces, and superclasses are currently represented; done requires an agreed and tested handling strategy.
Written by the indexing model from the issue text.
Assessment
- Domain
- reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100