[FML] Make logging available in constexpr contexts.#162343
[FML] Make logging available in constexpr contexts.#162343chinmaygarde merged 2 commits intoflutter:masterfrom
Conversation
Asking if the logs should be emitted and killing the process (say on unreachable statements) wasn't constexpr. However we managed to use these in constexpr context. As I understand (I am unsure), this was because of https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2022/p2448r2.html which is available in C++23. This technique makes the methods constexpr safe.
|
It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!). If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix? Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group. |
|
No change in functionality. |
| if (true_arg) { | ||
| KillProcess(); | ||
| } | ||
| #if defined(_MSC_VER) && !defined(__clang__) |
There was a problem hiding this comment.
This could be std::unreachable. But that is C++23 as well.
engine/src/flutter/fml/logging.h
Outdated
| // kLogFatal and above is always true. | ||
| bool ShouldCreateLogMessage(LogSeverity severity); | ||
|
|
||
| constexpr bool ShouldCreateLogMessage2(LogSeverity severity, bool true_arg) { |
There was a problem hiding this comment.
Include Constexpr in the name of these functions so it's clear why the wrappers exist.
Asking if the logs should be emitted and killing the process (say on unreachable statements) wasn't constexpr. However we managed to use these in constexpr contexts. As I understand, this was because of https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2022/p2448r2.html which is available in C++23. This technique makes the methods constexpr safe in C++17.