time.round-to-increment

def round_to_increment(minutes: int, increment: int, mode: RoundingMode) -> int

from fune.time.round_to_increment import round_to_increment  # time.round-to-increment@^1

from .math_round_div import round_div  ← from math.round-div ^1.0.0 · built alongside by fune
from .math_round_div_types import RoundingMode


def round_to_increment(minutes: int, increment: int, mode: RoundingMode) -> int:
    """Round a duration to a whole number of billing increments. The rounding is
    math.round-div's, so "half-up" here is the same rule as for money.
    """
    if isinstance(minutes, bool) or not isinstance(minutes, int) or minutes < 0:
        raise ValueError("minutes must be a non-negative integer, received %s" % (minutes,))
    if isinstance(increment, bool) or not isinstance(increment, int) or increment < 1:
        raise ValueError("increment must be a positive integer, received %s" % (increment,))
    return round_div(minutes, increment, mode) * increment

Install

fune build

With that line in your source, in a Python project (language python in fune.project), fune build resolves it and its 1 dependency, pins them in fune.lock, downloads only the Python package of each, and builds the code above into your project’s .fune/build, one readable file per capability with a header linking back here. Or pin a range in fune.project and build in one step:

fune add time.round-to-increment

The manifest, vectors and README with only the Python implementation. Install it without the registry with fune add ./time.round-to-increment-1.0.0-python.fune, or fetch it from a terminal with fune pull time.round-to-increment@1.0.0:python.

The whole function, every language, is one file too: time.round-to-increment-1.0.0.fune, 7,541 bytes, sha256 a025300b5b63a666a8089af6172507925276781f65c341183991b49c65834fc8. It installs into a project of any language.

# fune: before time.round-to-increment

# fune: after time.round-to-increment

# fune: replace math.round-div in time.round-to-increment

# fune: step time.round-to-increment after <n|label>

More from the author

- `up`: any part of a unit bills as a whole one. The usual rule for professional time. - `down`: only completed units count. - `half-up`: nearest unit, a tie (exactly half a unit) goes up. This is "nearest". - `half-even`: nearest unit, a tie goes to the even number of units, so ties do not bias a long timesheet upwards.

Rounding applies to the one duration you pass. Round each entry and then add, or add and then round, but know which your terms of business say: seven 3-minute calls rounded up in six-minute units bill 42 minutes one way and 24 the other.

Zero stays zero in every mode. A minimum charge ("at least one unit per call") is a business rule on top of this, not rounding. Durations are never negative; minutes below zero and an increment below one are errors.

Files