Should `cast_{un,}signed()` be considered an `as` cast for linting purposes?

[ojeda]

cast_signed() and cast_unsigned() are stable since 1.87.

They produce the same result as an as cast, but they ensure that the bit-width remains the same.

Should lints like cast_possible_wrap, cast_abs_to_unsigned and cast_sign_loss consider the new cast_{un,}signed() as as casts too?

Should this be configurable?

Related: #14974.

[nk9]

@rustbot label S-needs-discussion

[Rua]

Since these new methods are meant to be fixes applied by cast_sign_loss and cast_possible_wrap (to be implemented by #15384), treating them the same would lead to an infinite fix loop.

[Jarcho]

cast_abs_to_unsigned should probably check for it, but the others are linting because as casts have multiple different meanings.