dmakarov
dmakarov
Many Move smart contracts are parameterized by the type of an asset they're handling, e.g. Coin, where Coin can be any particular token type. That is to say, generic structs...
Sounds good to me. We definitely can postpone support of generic entry functions. I added a small example using a generic entry function in #355. It seems currently this function...
Makes sense. My mistake, not paying due attention.
When I compile unit tests using move-cli with Solana backend., everything compiles correctly, including the `test_ascii_chars`. Here's the generated llvm code for that test. ``` define private void @ascii_tests__test_ascii_chars() {...
Do we struggle to manage dependencies now?
> I have been thinking, that instead of adding a few new instructions and removing some others from BPF, it might be better to go with a [portable-code](https://en.wikipedia.org/wiki/Bytecode) approach directly....
We could change the BPF registers to unlimited number of virtual registers and do the register allocation at run-time. It would add some overhead, of course. I'm not sure it's...
> > What does this mean in practical terms? > > redefine the BPF instruction set completely? > > What I suggest is not to fork & modify BPF any...
> You mean as a form of SSA, right? What about an implicit operand addressing like a stack (FILO) or queue (FIFO) Yes, this essentially echoes your suggestion of staying...
> @dmakarov How long do you think the last 4 items in the issue description would take to implement? The support for signed division I think we already have enabled...