jolestar
jolestar
I also want to propose this, and I suggest maintaining a multi-language version at https://github.com/move-language/move/tree/main/language/documentation/book. @sblackshear @wrwg
As mentioned at https://github.com/move-language/move/pull/416 > We should add 0x prefix to ModuleId str, but should not use short_str in the output format, because 0x1 != 0x00000000000000000000000000000001 in str presentation, this...
I support unifying all address output format, and this PR is part of that goal. I think supporting more input formats and consistent output format is a simple strategy to...
I support `one module per format`
> Another approach we could consider here (that would make the testing burden a bit less onerous) is to implement this via `native` functions that wrap the Rust `hex` library....
I think we should distinguish two scenarios: ### First: Asset scenarios, such as Token/Coin/NFT. I call it as `Free State`, the state can move between modules. We can use the...
@tnowacki Agree, we can use `enum` to replace the interface in `Strategy Pattern` if we know all the implementations. > That being said, the interfaces on the module level like...
The `interface` best use case is the swap aggregator. if the aggregator wants to dispatch a function invocation to the swap, all swaps need to implement a swap public API...
We try to implement this on Move but have some complex problems. One motivation is to deploy Move modules in the Move module. We want to update the Move modules...
@shiftkey yes, I expect client default behavior is like this: