Forcing ScoreTypeGroup
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 412
- Avg merge
- 6d 10h
- Merged PRs (30d)
- 3
Description
Now all scoretypes except Sum are ScoreTypeGroup. Moreover, all non-group scoretypes can be regarded as scoretypes with one group.
Regarding the rule of IOI 2016, I think we will have to write more subtask-oriented code. Forcing all scoretypes to be ScoreTypeGroup may help this. For example, moving Sum to GroupSum like in #620 makes Sum unnecessary and we can concentrate on ScoreTypeGroup.
Moreover we may introduce different scoretypes for subtasks in a task, if it is useful... (Actually Japanese OI committee have made one or two such tasks, if I remember correctly.)
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
Start by reviewing the current Sum and ScoreTypeGroup implementations, then read the related change in #620. Map how scoretypes and subtasks are represented before proposing a unified design; done requires an agreed approach for replacing or subsuming Sum and supporting subtask-specific scoretypes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100