Add support for contexts
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Review the existing clock API and Go's context.WithTimeout and context.WithDeadline behavior first. Define how context creation, expiry control, and the proposed tag should fit this library or a qzcontext sub-package; done means context deadlines can be deterministically advanced through the clock.
Written by the indexing model from the issue text.
Description
This might be a stretch for this library, but it would be cool if we had support for contexts, whether directly in this package or a sub-package like qzcontext.
Now, rather than doing context.WithTimeout you'd do clock.Context.WithTimeout(ctx, duration, "tag") (likewise for deadline) and be able to control expiry by advancing the clock.
- Dominant language
- Go
- Stars
- 273
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from coder/quartz
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
containerd/containerd#14476 · 1 comment ·
Maintainers usually reply within 1 day
-
kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ome-projects/ome#1242 ·
Maintainers usually reply within 1 day
-
copy design-review mac P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
tosunlab/hisarapp-core#510 ·