`a || b` only evaluates b if a is false. `a | b` always evaluates both a and b. If a and b are of type bool, || is usually what you want, so clang now warns on `|` where both arguments are of type bool. This warning fires twice in harfbuzz. In both cases, `|` is used intentionally, with a comment explaining this. Slightly reorder the code a bit to make the compiler happy, and to make it obvious even without a comment that both calls should be evaluated. No intended behavior change. |
||
---|---|---|
.ci | ||
.circleci | ||
.github/workflows | ||
docs | ||
m4 | ||
perf | ||
src | ||
subprojects | ||
test | ||
util | ||
.clang-format | ||
.codecov.yml | ||
.editorconfig | ||
AUTHORS | ||
BUILD.md | ||
CMakeLists.txt | ||
CONFIG.md | ||
COPYING | ||
Makefile.am | ||
NEWS | ||
README | ||
README.md | ||
README.mingw.md | ||
README.python.md | ||
RELEASING.md | ||
TESTING.md | ||
THANKS | ||
TODO | ||
autogen.sh | ||
configure.ac | ||
git.mk | ||
harfbuzz.doap | ||
meson.build | ||
meson_options.txt | ||
mingw-configure.sh | ||
replace-enum-strings.cmake |
README.md
This is HarfBuzz, a text shaping library.
For bug reports, mailing list, and other information please visit:
For license information, see COPYING.
For build information, see BUILD.md.
For custom configurations, see CONFIG.md.
For test execution, see TESTING.md.
Documentation: https://harfbuzz.github.io