-
Notifications
You must be signed in to change notification settings - Fork 5
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
rholang 1.1 -> 1.0 dev tool a la babel #48
Comments
We could publish special pre-release with Rholang 1.1 which can be used in evaluated mode to get translation to desugared syntax. For example this code evaluated with Rholang 1.1 let x <- 1 ; y <- 2 ; z <- 3 in {
(*x, *y, *z)
} produces this output match [1] {
[x0] => {
match [2] {
[x1] => {
match [3] {
[x2] => {
(x0, x1, x2)
}
}
}
}
}
} |
Exactly. I was thinking of a standalone jar a la But anything that can be used from a batch dev tool (npm script, makefile, ...) is fine. |
@Bill-Kunj I'm suggesting to publish a pre-release with all the artifacts (Docker image, deb package, ...) so it can be used in VSCode extension or with |
This sounds like a great start. |
Not being pushy, but I really, really want to try this out. When can I start using it? |
Rholang 1.1 pre-release (special build) is published: v0.12.4+rholang-1.1-rc1. Docker image has tag name with It's based on v0.12.4 version with some small updates not related to Rholang. These test can help to understand how the new syntax is desugared to Rholang 1.0.
Enjoy! 🥳 |
Thanks!
I'm struggling to figure out how. Help, please? I put the example above in
Now what? How do I convert it to rholang 1.0 using I tried:
then I tried:
|
@dckc You need to run an instance of RNode and call gRPC method eval. This is what CLI eval method is doing. So first start standalone instance.
When it's up (unfortunately after the blockchain part is ready) you can call eval to that instance with the same container, so escape all of networking setup. Eval is on private port, so port 40402.
|
We have a rholang 1.1 implementation in the form of a source-to-source translation to rholang 1.0. Getting this integrated into validator nodes on mainnet involves lots of coordination that will understandably take time, but meanwhile, much like JavaScript developers use babel to translate new features to syntax understood by deployed browsers, we should expose the rholang 1.1 to 1.0 translator as tool so that developers can write rholang 1.1 and translate it rholang 1.0 automatically for deployment.
We could, for example, integrate that with the Rholang Playground - RChain.
ref:
The text was updated successfully, but these errors were encountered: