I have a consteval function that verifies at compile time that the passed const char * is a valid, null-terminated string matching a specific format. The reason the pointer arithmetic in the logic is safe is because it can only be evaluated at compile time, where reading past the end of an improperly terminated string will result in a compiler error, not an invalid memory access.
I can wrap the offending pointer arithmetic with UNSAFE_BUFFERS(), but that would mean that the code would still compile if consteval were changed to constexpr in the future.
Would it make sense for the unsafe-buffers plugin to suppress diagnostics inside of consteval functions?