Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Import work from gnolang/gno#1092.
I'm pondering a few things about our setup:
misc/
,gnovm/
, new top-level namespace, or its own repo?gno
?.gnoffee
files and gives us output. You can see it on screen or save it using-w
. But here's the twist: it currently blends the new bits with all the.gnoffee
scripts, creating a full.go
file. Another idea is to just pinpoint and add what's missing, resulting in agnoffee.gen.go
file. I'm weighing up both approaches and would appreciate your insights.Any feedback or even a chat about it would be great. cc @gnolang/tech-staff @gnolang/core-contributors
Suggestion for reviewers: checkout the txtar tests: https://github.com/gnolang/gno/pull/1092/files#diff-a9299fce0ae91a6a0eb6e0bfc51ab83a51116d452703e4c82f473f1e933dff4f
Addresses gnolang/hackerspace#22
Addresses gnolang/gno#1075
Depends on gnolang/gno#1093 (tests fail on go1.19)