[类型 / Types] 按需评估 calendar 算术 / evaluate calendar arithmetic on demand
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 0
- Forks
- 0
- Avg merge
- 57m
- Merged PRs (30d)
- 209
Description
中文说明
按需评估 date/timestamp 的显式月/年 calendar 算术与转换。不得引入隐式本地时间、时区或 DST 规则；需要真实账期、续费或排期场景先冻结月底、闰年和时区边界。
当前已有 timestamp ± duration，足以覆盖固定时长运算。本 issue 无 milestone，P2 deferred。
English Description
Evaluate explicit month/year calendar arithmetic and date/timestamp conversions on demand. Do not introduce implicit local time, time zones, or DST rules. Require a real billing, renewal, or scheduling workload to freeze end-of-month, leap-year, and zone boundaries first.
Existing timestamp ± duration covers fixed-duration arithmetic. No milestone; P2 deferred.
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
No files or tests are named. Start by reviewing the existing timestamp ± duration behavior and identify a concrete billing, renewal, or scheduling workload before defining calendar arithmetic and date/timestamp conversion semantics. Done means the end-of-month, leap-year, timezone, and DST boundaries are explicitly decided before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100