[taepper]

Rationale for this change

This fixes #54924. An extension array would not round-trip correctly through ArraySpans as a test demonstrates.

What changes are included in this PR?

This fixes the HasVariadicBuffers implementation to correctly handle extension types. A test demonstrating the fix is also included.

The fix follows the implementation of ArraySpan::SetMembers, where the same additional case for extension types is included

Are these changes tested?

Yes. By the existing test suite plus an additional test.

Are there any user-facing changes?

None other than the bug fix.

Was AI used for this PR?

In accordance to the AI generation guidelines, please disclose below whether and how AI was used in this PR.

PR code and description written by:

• Human
• AI

Reviewed before submission by:

• Human
• AI
• Not reviewed

An LLM suggested the second fix for

  if (type_id == Type::STRING_VIEW || type_id == Type::BINARY_VIEW) {

in ArraySpan::SetMembers, which does look correct to me.

• GitHub Issue: [C++] HasVariadicBuffers should respect extension types #54924

[github-actions]

⚠️ GitHub issue #54924 has been automatically assigned in GitHub to PR creator.