[clang-format] Changed formatting of trailing return type between version 18 and 19

[carlosgalvezp]

Hi!

We are testing bumping our clang-format installation from version 18 to 19, and notice a fair amount of churn, without changing the config file. In particular, this type of code:

auto foo(Type a, 
         Type b) -> std::enable_if<....>
{}

Gets transformed into:

auto foo(Type a, Type b) 
    -> std::enable_if<...>
{}

Do you know if there's a newly added option that controls this behavior, or what could be the reason for this change?

Thanks!

[llvmbot]

@llvm/issue-subscribers-clang-format

Author: Carlos Galvez (carlosgalvezp)

Hi!

We are testing bumping our clang-format installation from version 18 to 19, and notice a fair amount of churn, without changing the config file. In particular, this type of code:

auto foo(Type a, 
         Type b) -> std::enable_if<....>
{}

Gets transformed into:

auto foo(Type a, Type b) 
    -> std::enable_if<...>
{}

Do you know if there's a newly added option that controls this behavior, or what could be the reason for this change?

Thanks!

[rymiel]

You have to provide a config and the full lines of code (we don't need the whole file)

I suspect it might be related to e00d32a and 438ad9f and might already be fixed but we can't tell you unless you provide more info or unless you test on main