[Chapel Merge] User error for unsupported field detuple

Branch: refs/heads/main
Revision: bbba52e7f24d253c78330276a56099870d6b0af4
Author: DanilaFe
Link: User error for unsupported field detuple by DanilaFe · Pull Request #27984 · chapel-lang/chapel · GitHub
Log Message:
User error for unsupported field detuple (#27984)

Closes Collection of codes that generate Internal error · Issue #9987 · chapel-lang/chapel · GitHub in favor of
How should de-tupling fields work, if at all? · Issue #27983 · chapel-lang/chapel · GitHub.

Since it turns out the semantics of tuple field initialization are
non-trivial, disallow them for now. This is an improvement over the
current state on main, where such fields produce internal errors.

Reviewed by @jabraham17 -- thanks!

Testing

  • dyno tests
  • paratest

Compare: Comparing dbfb45024375bf01531f263fd987733b57e03acd...6994ea8539f11b233dc0c720a170dc59f0ab09cd · chapel-lang/chapel · GitHub

Diff:
M frontend/lib/uast/post-parse-checks.cpp
M frontend/test/uast/testStringify.cpp
A test/errhandling/errorMessages/throwQuery.chpl
A test/errhandling/errorMessages/throwQuery.good
A test/errhandling/errorMessages/throwQuery.prediff
A test/functions/accidentalCapture.chpl
A test/functions/accidentalCapture.good
A test/types/range/lydia/badRange-real-lower.chpl
A test/types/range/lydia/badRange-real-lower.good
D test/types/records/tupleFields/detupleFieldDecl.bad
D test/types/records/tupleFields/detupleFieldDecl.future
M test/types/records/tupleFields/detupleFieldDecl.good
A test/types/tuple/errors/genericArrayAsTupleSize.chpl
A test/types/tuple/errors/genericArrayAsTupleSize.good
A test/types/tuple/errors/genericArrayAsTupleSize.prediff
A test/types/tuple/errors/invalidTupleSizeExpr.chpl
A test/types/tuple/errors/invalidTupleSizeExpr.good
https://github.com/chapel-lang/chapel/pull/27984.diff