compiler: allow unnamed -> named tuples conversions on name match

[aleksisch]

It's useful to be able to not repeat yourself. If tuple names exactly match variable names we want to assign we should allow to write unnamed tuple. See tests for more details.

Closes #2641

[borisbat]

1. documentation. update tuple.rst (or whatever its called) - when it would match, and what it would and would-not match
2. language tutorial on tuples should expand on this
3. update serializer version

[Copilot]

Pull request overview

This PR adds compiler support for treating bare-variable tuple literals as named tuples when their variable names match the target tuple field names, addressing #2641.

Changes:

• Tracks shorthand tuple field names during parsing.
• Seeds tuple record types during inference for typed variable initialization and function-call matching.
• Adds language tests for successful shorthand tuple use and mismatch failure.

Reviewed changes

Copilot reviewed 17 out of 17 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
utils/dasFormatter/ds_parser.ypp	Mirrors tuple shorthand metadata collection in formatter parser.
tests/language/tuple.das	Adds successful shorthand tuple language tests.
tests/language/failed_tuple_shorthand_mismatch.das	Adds expected-failure test for mismatched shorthand names.
src/parser/parser_impl.h	Declares shorthand tuple name collection helper.
src/parser/parser_impl.cpp	Implements shorthand tuple name collection from bare variables.
src/parser/ds2_parser.ypp	Adds shorthand metadata collection to gen2 parser grammar.
src/parser/ds2_parser.cpp	Regenerated gen2 parser output.
src/parser/ds_parser.ypp	Adds shorthand metadata collection to parser grammar.
src/parser/ds_parser.cpp	Regenerated parser output.
src/builtin/module_builtin_ast_serialize.cpp	Serializes new tuple shorthand metadata.
src/ast/ast.cpp	Preserves shorthand metadata when cloning tuple expressions.
src/ast/ast_infer_type.cpp	Seeds shorthand tuple record types from typed let/global initializers.
src/ast/ast_infer_type_make.cpp	Promotes matching shorthand names into tuple record names.
src/ast/ast_infer_type_function.cpp	Attempts shorthand-based function-call rematching.
include/daScript/ast/ast_infer_type.h	Declares new inference hooks/helpers.
include/daScript/ast/ast_expressions.h	Adds tuple shorthand metadata storage.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[aleksisch]

I don't see how to resolve it cleanly.

What we do now: promote everything to named.

What you suggest: promote to named one by one, attempting to match function.

Your scenario misses the case:
foo((x,y), (a,b)) -> foo(tuple<x:int;y:float>, tuple<a:int;b:float>)
My scenario misses case:
foo((x,y), (a,b)) -> foo(tuple<x:int;y:float>, tuple<int;float>)

[borisbat]

how do i tell it to explicitly be nameless. say there are TWO push functions
push ( a : tuple<int,float> )
push ( a : tuple<edi:int, distSq:float> )
and i write push((eid,distSq)) - which one would it pick?

[aleksisch]

We give priority to unnamed tuples:

if (functions.empty() && generics.empty() && trySeedTupleShorthand(expr)) {

So we will try this feature only if nothing matched earlier.

This code works fine and prints 1. I will add it to tests anyway.

def foo(x : tuple<int; float>) {
    print("1")
}

def foo(x : tuple<x: int; y: float>) {
    print("2");
} 

[export]
def main{
    var x = 123
    var y = 321.
    foo((x, y))
}

[borisbat]

document? test?