tree f8eced9b6087abdab62e45fb4bd2aaaecef3b122
parent 6e96e12bc5e08c7fc434eb93e6e0fcadc3ee3cc8
author Donald Chai <dchai@google.com> 1659496986 -0700
committer Donald Chai <dchai@google.com> 1659543573 +0000

Use line position when that's all we have.

TextPosition is a more general class to store byte offset + line+column.
It's both wasteful and misleading to store e.g. 0 as the byte offset in
there.

FWIW LinePosition is still somewhat wrong when ProGuard maps are
filtered upstream, but I've opted to keep the existing semantics for
other use cases (i.e. error messages for -applymapping).

Bug: b/240037206
Change-Id: I93ccdd10af96525c8df0dcd323a6000394925c39