-
Notifications
You must be signed in to change notification settings - Fork 8
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
Updating of tinyGo => cosmwasm #11
Comments
Thank you for the update @KamiD As to #458 don't block on that and please do the same in cosmwasm simulate, disabling it. The way to disable without forking is setting the feature flag to default-cranelift. This will turn off enforcing no floats (and also disable gas metering). I will look into making the json lib float-free |
cool, I will try it in cosmwasm simulate~ |
Great. You just need this line in
|
In general, I don't see many PRs that I can review, and work seems to happen on branches, so it is a bit hard to contribute. If there were a more clear workflow (where any important branch has a PR, even in draft mode), it is easier to see where there work is. When I find time, I would love to figure out how to deal with the float issue, ideally by making the json library float-free, so we can keep the VM as is, and generate "legal" code from TinyGo. But it would be good to know what branch to fork from when trying that. |
OK, I will cleanup those branches, make a clear workflow, all works will doing based a PR~ |
Thank you @KamiD If all important work is either on master (or develop if you prefer) or on a open PR, that makes it easier to track. Ideally PRs are smaller and merged frequently, so I can make PRs off master to eg. change the json codec to not produce floating point ops without worrying about which branch to merge off of. Other than that, I am open to any flow. But it may be helpful to create a number of issues that need doing and make a project board for them. (My experience in other remote teams) But you can choose the process that works best for you. My PR #9 is still hanging for a while, and I don't know if it will ever be merged, or if there is other work building off of it (or an alternate form of it) in another branch. |
Hi @ethanfrey |
BTW: Now our working branch is |
alpha-json branch has merged into Alpha |
I just merged all of this except uint128 into master. That has it's own issue. I will add CI and an example hackatom contract to match the rust demo. |
Overview
This issue is used for progress updating in tinyGo => cosmwasm
it will update every 2 weeks util first public version released
Requirement of alpha version (in developing)
Updating simulate tool depends version of cosmwasm-vm and cosmwasm-std from v0.8 to 0.10
Developing json lib for tinyGo => wasm, support Marshal and Unmarshal
Developing API Support between cosmwasm-go and cosmwasm, based on cosmwasm-v0.10
Debugging loading process in wasmd, make sure every func
check***
will passedcw-compile
to process all illegally symbol export or import, check*** will passed now~Building a development framework of contract which is writing by Go
Fix Issue458 in cosmwasm
Add messages analyze support such as Staking\Bank\Wasm
Add
SafeMath
supportAdd Type of
Uint128
support on tinyGo (using BigInt?)Translating return message in
init\handle\query
The text was updated successfully, but these errors were encountered: