comparison mercurial/dirstateutils/timestamp.py @ 48398:111098af6356

dirstate-item: add a "second_ambiguous` flag in the mtime tuple

This will be used to support the `mtime-second-ambiguous` flag from dirstate
v2. See format documentation for details.

For now, we only make it possible to store the information, no other logic have
been added.

Differential Revision: https://phab.mercurial-scm.org/D11842

48397:8d585aa9becf

    `subsecond_nanoseconds`: number of nanoseconds since `truncated_seconds`.
    When this is zero, the sub-second precision is considered unknown.
    """

    def __new__(cls, value):
        truncated_seconds, subsec_nanos = value
        value = (truncated_seconds & rangemask, subsec_nanos)
        return super(timestamp, cls).__new__(cls, value)

    def __eq__(self, other):
        raise error.ProgrammingError(
            'timestamp should never be compared directly'

    else:
        billion = int(1e9)
        secs = nanos // billion
        subsec_nanos = nanos % billion

    return timestamp((secs, subsec_nanos))


def reliable_mtime_of(stat_result, present_mtime):
    """same as `mtime_of`, but return None if the date might be ambiguous

48398:111098af6356

    `subsecond_nanoseconds`: number of nanoseconds since `truncated_seconds`.
    When this is zero, the sub-second precision is considered unknown.
    """

    def __new__(cls, value):
        truncated_seconds, subsec_nanos, second_ambiguous = value
        value = (truncated_seconds & rangemask, subsec_nanos, second_ambiguous)
        return super(timestamp, cls).__new__(cls, value)

    def __eq__(self, other):
        raise error.ProgrammingError(
            'timestamp should never be compared directly'

    else:
        billion = int(1e9)
        secs = nanos // billion
        subsec_nanos = nanos % billion

    return timestamp((secs, subsec_nanos, False))


def reliable_mtime_of(stat_result, present_mtime):
    """same as `mtime_of`, but return None if the date might be ambiguous