List parameters about neo-mamba HOT 12 CLOSED

It's been a while so I'm going to let it sink in and try to remember why I took this approach. If I can't come up with a good reason then we can change it to use PACK (should also be cheaper)

from neo-mamba.

I'm not sure I understand what you're referring to. Can you elaborate or point to the code where this is happening?

from neo-mamba.

You mean this?

I'm open to suggestions on how you think we can improve it

from neo-mamba.

Sorry I'll try with a screenshot :) As you can see using last version of neo-mamba when passing a list as parameter It's using some opcodes I put in first message in the transaction script. But if I build It myself without those append/dup... It's still working so I'm wondering if there is something I'm missing?

from neo-mamba.

Can you share an example how you're building your array?

from neo-mamba.

I was using this on my side previously

class ScriptBuilderWithListSupport(vm.ScriptBuilder):
    def emit_push_list(self, items: list):
        for item in reversed(items):
            if type(item) is list:
                self.emit_push_list(item)
                continue
            self.emit_push(item)
        self.emit_push(len(items))
        self.emit(vm.OpCode.PACK)

    def emit_dynamic_call_with_args(self, script_hash, operation: str, args) -> None:
        self.emit_push_list(args)
        self.emit_push(0xF)
        self.emit_push(operation)
        self.emit_push(script_hash.to_array())
        self.emit_syscall(vm._syscall_name_to_int("System.Contract.Call"))

from neo-mamba.

This?

    def emit_push_list(self, items: list):
        for item in reversed(items):
            if type(item) is list:
                self.emit_push_list(item)
                continue
            self.emit_push(item)
        self.emit_push(len(items))
        self.emit(vm.OpCode.PACK)

from neo-mamba.

Yeap cheaper and more beautiful that's why I opened an issue :D

from neo-mamba.

It's been a while so I'm going to let it sink in and try to remember why I took this approach. If I can't come up with a good reason then we can change it to use PACK (should also be cheaper)

I can't think of anything at the moment, so open to accept a PR if you'd like

from neo-mamba.

Something like this? #255

from neo-mamba.

It's been a while so I'm going to let it sink in and try to remember why I took this approach. If I can't come up with a good reason then we can change it to use PACK (should also be cheaper)

I can't think of anything at the moment, so open to accept a PR if you'd like

The previous implementation with DUP and APPEND was used to invert the order of the emitted items . The solution from @NeoDashboard emits the items directly in the correct (inversed) order and is cheaper.

from neo-mamba.

Fixed in #256

from neo-mamba.