feat(examples): add moul/xmath

[moul]

Experimenting with Go-based code generation in the examples/ folder.

[Gno2D2]

🛠 PR Checks Summary

All Automated Checks passed. ✅

Manual Checks (for Reviewers):

• IGNORE the bot requirements for this PR (force green CI check)

Read More

🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers.

✅ Automated Checks (for Contributors):

🟢 Maintainers must be able to edit this pull request (more info)

☑️ Contributor Actions:

1. Fix any issues flagged by automated checks.
2. Follow the Contributor Checklist to ensure your PR is ready for review.
   • Add new tests, or document why they are unnecessary.
   • Provide clear examples/screenshots, if necessary.
   • Update documentation, if required.
   • Ensure no breaking changes, or include BREAKING CHANGE notes.
   • Link related issues/PRs, where applicable.

☑️ Reviewer Actions:

1. Complete manual checks for the PR, including the guidelines and additional checks if applicable.

📚 Resources:

• Report a bug with the bot.
• View the bot’s configuration file.

Debug

Automated Checks

Maintainers must be able to edit this pull request (more info)

If

🟢 Condition met
└── 🟢 The pull request was created from a fork (head branch repo: moul/gno)

Then

🟢 Requirement satisfied
└── 🟢 Maintainer can modify this pull request

Manual Checks

**IGNORE** the bot requirements for this PR (force green CI check)

If

🟢 Condition met
└── 🟢 On every pull request

Can be checked by

• Any user with comment edit permission

[n0izn0iz]

LGTM

Maybe we could add a git workflow to check that the generated code in examples is synced?

[moul]

@n0izn0iz good idea, sholud be good with my last commit.

[n2p5]

LGTM

[moul]

Despite the LGTMs (thank you, guys), I'm waiting for @thehowl's opinion before merging.

[thehowl]

Long-term, I think we can have a way to generate code using gno; seeing as there is no fs access, I'd imagine something like //gno:generate myGeneratorFunc() > output.gen.gno. But this is non-trivial and something to be understood later. This can work for now and is useful.

One thing to consider is that .go files are not currently included in MemPackages (outside of standard libraries, where we want them because of native bindings). It may make sense to start including .go files, as long as we exclude transpiled gno code.

[moul]

For the long-term gno-powered generation, I have two ideas in mind that I believe I have already started in a draft PR.