[Scheduling] Allow cloning of problem instances
- Dominant language
- C++
- Stars
- 2.2k
- Forks
- 524
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 46
Description
Test whether the copy constructor and assignment operator is usable with `Problem` instances. If not, we should introduce a `clone()` method on the problem hierarchy, to be overridden by subclasses to achieve the same effect.
Contributor guide
No contributing guide indexed for this repository
Research direction
Inspect the Problem hierarchy and determine whether its copy constructor and assignment operator can be used for scheduling problem instances. If they are not usable, trace the subclasses and assess the clone() design described in the issue. Done means either confirming existing copying works or adding a consistent cloning approach across the hierarchy, with coverage for representative Problem subclasses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100