Strange formatting of a requires containing an array

[mordante]

I tested with clang-format after https://reviews.llvm.org/D113319 landed and found some issues in new code. This looks similar to #53820, but I'm not sure whether it's the same issue.
I used this config

BasedOnStyle: LLVM
  
---
Language: Cpp
Standard: c++20

Code (for libc++ so uses __ugly_names)

template <class _Context, class _Tp>
  requires is_array_v<_Tp> &&
           same_as<_Tp, typename _Context::char_type[extent_v<_Tp>
]> consteval auto
  __make_storage_type() {
  return __storage_type<basic_string_view<typename _Context::char_type>>{};
}

I would expect this part to be on one line same_as<_Tp, typename _Context::char_type[extent_v<_Tp>]>
Using parens solves the issue

template <class _Context, class _Tp>
  requires(is_array_v<_Tp> &&
           same_as<_Tp, typename _Context::char_type[extent_v<_Tp>]>)
consteval auto __make_storage_type() {
  return __storage_type<basic_string_view<typename _Context::char_type>>{};
}

[llvmbot]

@llvm/issue-subscribers-clang-format

[llvmbot]

@llvm/issue-subscribers-bug

[HazardyKnusperkeks]

It has definitely the same reason as #53820, but if the same fix applies I have to check the coming days.

[HazardyKnusperkeks]

It has definitely the same reason as #53820, but if the same fix applies I have to check the coming days.

So this was a lie. The problem is the nested template, this one will take some time to figure out.
But using an array in the top level of a constraint expression will also have a problem.

[HazardyKnusperkeks]

Just to give a heads up. This is gonna take long. For once because it is a big problem to solve (which will help to clean clang-format), but also because I have to do other stuff right now. I'm sure we make it to the release of LLVM 15.

[mordante]

Thanks for the heads up. I'll use the parens, at style I like slightly better. (They were removed to format better with clang-format at that time. Now it formats better with parens.)

[JohelEGP]

Is this fixed? According to #53819 (comment), it's my same issue. I was able to remove the workarounds to get the same formatting I had before.

[HazardyKnusperkeks]

This one might be fixed, but the conceptual error is still there. Just the most likely stuff works.
If everything on your code works fine, you can close this issue. I have my todo list somewhere else.