Listing subtypes semantically in the exports list
Open
Nobody has claimed this yet.
Core
Documentation
- Dominant language
- Macaulay2
- Stars
- 435
- Forks
- 297
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 11
Description
The title is obscure, so I'll explain what I want with a manipulated example:
Here, `AffineVariety` and `ProjectiveVariety` are subtypes of `Variety` and the list should reflect this.
Contributor guide
No contributing guide indexed for this repository
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
Start by tracing the exports list and how subtype relationships are represented in Macaulay2. Use the example involving Variety, AffineVariety, and ProjectiveVariety as the expected behavior; done means the list reflects those semantic subtype relationships.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100