Golang working group / Gnolang 1.x

[moul]

Here are some relevant links and discussions regarding Golang initiatives we could engage in:

• Proposal: Make Go2 better implement the Object-capability model for security -- Link
• Master Issue of Go1 Issues to consider -- Link
• Proposal: spec: remove complex numbers -- Link
• Proposal: use a value other than nil for uninitialized interfaces -- Link
• Proposal: Go 2: Add typednil keyword for checking whether an interface value is a typed nil -- Link
• Proposal: Go 2: capability annotations -- Link
• Proposal: Go 2: read-only types -- Link
• Improve reflection system (so we can complete go2gno and gno2go)

Things we consider for post-release versions of Gnolang (Gno1.x)

• Things above
• Support new types like bigints natively
• Make gno2go similar to CoffeeScript/TypeScript and generate good usage Go code

---

There is a meta issue on the main repo that could help a lot addressing all those topics, see: gnolang/gno#972.

[moul]

New proposals (label filter):

• feat: another improved error handling proposal gno#1018
• proposal: extending const behavior gno#919

[mvertes]

For reference, golang/go#33702 to have deterministic execution in Go.

[moul]

Let's create a newsletter featuring the latest updates, including both successes and challenges, and current progress (possibly quantified by percentage). This newsletter will also highlight ongoing obstacles and propose future concepts. It will comprehensively cover our Go interpreter projects: gnovm, gnors, parscan, and possibly yaegi.

This will be a straightforward engineering-focused communication, free from marketing.

We plan to share these reports regularly on Gopher Slack, Twitter and Reddit, allowing interested individuals to discover, engage, and potentially contribute at their own pace.

Additionally, we'll craft a technical blog post to introduce this newsletter initiative. It will reiterate our challenges and our vision of developing an interpreted Go language, not just for blockchain applications, but also as a competitor to Python.

[thehowl]

Let's create a newsletter featuring the latest updates, including both successes and challenges, and current progress

Who writes this newsletter? Is it a rota of the engineering team + devrels?

Is this endeavour not very closely related to The More You Gno? Would it replace/evolve The More You Gno?

[michelleellen]

Hey @moul @thehowl I am very keen on having this, I would also suggest though we try to create this content and then submit it to GoWeekly newsletter. I also think it is worthwhile bringing back the working group.

Maybe to add to the devrel agenda today!