diff options
| author | Justin Bogner <mail@justinbogner.com> | 2025-10-01 12:15:46 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-10-01 19:15:46 +0000 |
| commit | 78c65545d4694e043b593e4cca7c7281a639247b (patch) | |
| tree | 925b95f6b8fc1df128f6aa08c67f8ed4b2fffc24 /lldb/packages/Python/lldbsuite/test/dotest.py | |
| parent | 9e04291fd20489882259625ec327b87ecef6fa8c (diff) | |
| download | llvm-78c65545d4694e043b593e4cca7c7281a639247b.zip llvm-78c65545d4694e043b593e4cca7c7281a639247b.tar.gz llvm-78c65545d4694e043b593e4cca7c7281a639247b.tar.bz2 | |
[AST] Give `CharUnits::operator%` a consistent type. NFC (#160781)
Update the `operator%` overload that accepts `CharUnits` to return
`CharUnits` to match the other `operator%`. This is more logical than
returning an `int64` and cleans up users that want to continue to do
math with the result.
Many users of this were explicitly comparing against 0. I considered
updating these to compare against `CharUnits::Zero` or even introducing
an `explicit operator bool()`, but they all feel clearer if we update
them to use the existing `isMultipleOf()` function instead.
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/dotest.py')
0 files changed, 0 insertions, 0 deletions
