build(deps): bump github.com/goplus/xgo from 1.6.0 to 1.6.2

[dependabot]

Bumps github.com/goplus/xgo from 1.6.0 to 1.6.2.

Release notes

Sourced from github.com/goplus/xgo's releases.

v1.6.2

What's Changed

features:

• Map Field Access with Comma‐ok Propagation (#2572) by @​xushiwei in #2574 #2573

docs:

• doc: struct vs. tuple by @​xushiwei in #2578 #2579 #2580

changes:

• demo/tupletype by @​xushiwei in goplus/xgo#2565
• XGo_Env: support fileline param (token.Position) by @​xushiwei in goplus/xgo#2567
• tryFileLine: remote log & add comments by @​xushiwei in goplus/xgo#2568
• tryFileLine: use relFile of fileName by @​xushiwei in goplus/xgo#2569
• XGo_Env: remove fileline support by @​xushiwei in goplus/xgo#2570

Full Changelog: goplus/xgo@v1.6.1...v1.6.2

v1.6.1

What's Changed

Unified Declaration Syntax via Tuples

This update introduces a paradigm shift in the language's syntax by leveraging Tuples to unify the definitions of functions, types, and variables. By treating everything—from parameters to standalone types—as a tuple, we have achieved a truly "orthopedic" language design where data structures and logic share a single DNA.

1. The Core Philosophy: "Everything is a Tuple"

The cornerstone of this update is the realization that a type, a named field, and a collection of fields are all just variations of a tuple. Specifically, the following are semantically identical:

• T (a raw type)
• (T) (a single-element tuple)
• (name T) (a named single-element tuple)

In this version, $T \equiv (T) \equiv (name\ T)$. Whether you are defining a single integer or a complex set of parameters, you are working within the same tuple-based framework.

2. Functions as Tuple Transformations

Under this unified model, a function is no longer a special construct with its own unique grammar. Instead, a function is defined as a transformation from one tuple to another.

• Mapping: $Tuple_{in} \to Tuple_{out}$
• The Unit Tuple: If a function has no parameters or no return values, it simply interacts with the Empty Tuple ().

3. Unified Syntax in Action

By standardizing on tuples, the syntax for functions, types, and variables becomes perfectly symmetrical. Notice how the "shape" of the data remains constant across different keywords:

func run (timeout, maxRetries int, debug bool) (code int, err error)
type Config (timeout, maxRetries int, debug bool)
var cfg (timeout, maxRetries int, debug bool)
</tr></table> 

... (truncated)

Commits

• 9a88fde Merge pull request #2580 from xushiwei/q
• ca163e9 doc: tuple in minispec
• f24ece2 Merge pull request #2579 from xushiwei/q
• 814884b README fix
• ac6501b Merge pull request #2578 from xushiwei/q
• eb4d913 README: tuple
• 567d835 comment by gemini
• 206a903 doc: struct vs. tuple
• 1adae53 Merge pull request #2574 from xushiwei/q
• a5ae1d9 gogen v1.20.8: Go does not fully implement chained call safety
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.