Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extend stack type #6

Merged
merged 42 commits into from
Feb 3, 2023
Merged

Extend stack type #6

merged 42 commits into from
Feb 3, 2023

Conversation

barnjamin
Copy link
Owner

@barnjamin barnjamin commented Feb 1, 2023

  • add immediate arg positions in the case of errors
  • for labels I need their names
  • for ops that may branch I need the target labels names
  • need to know op names for each line
  • a list of ops that can terminate a program (err, return, etc.)
  • no-op line numbers
  • args ranges + arg type info
  • comments ranges

@barnjamin barnjamin force-pushed the extend-stack-type branch 3 times, most recently from 6281d99 to 0444f35 Compare February 1, 2023 18:11
@@ -28,13 +28,13 @@ import (
"github.com/algorand/go-algorand/protocol"
)

var docVersion = 8
var latestVersion = 8
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we're going to generate all versions, including the one after the current consensus version (which I think is correct). We can go back to a world that does not have this variable at all, and uses the value in logic.LogicVersion.

If we generate all these langspecs, we'll have to change the website to pick up the right one to show. (Maybe it should show them all somehow, but the "main" one should be the current mainnet's consensus value.

@barnjamin barnjamin marked this pull request as ready for review February 3, 2023 18:38
@barnjamin barnjamin merged commit 015bad4 into langspec-keywords Feb 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants