Handling tuple returns?

[JamesANZ]

Many functions return a bunch of parameters. Maybe we should add a tuple type or a way to explicitly write out the variables that are returned.

[JamesANZ]

Have added the tuple type in #162 but it doesn't have a way to interpret the args yet

[JamesANZ]

@colourful-land how about a type with something like this: tuple<[Any]>, similar to Kotlin/swift notation

[SmartLayer]

That means we will have an attribute type that is a tuple. That's a dangerous decision to make (more dangerous than, e.g. if we have an attribute type that is an array) because the consequence is huge. Let's try not to solve it in May.

[JamesANZ]

@colourful-land how about instead of a tuple we simply allow you to explicitly define multiple return args like uint,uint,string etc?

[SmartLayer]

@colourful-land how about instead of a tuple we simply allow you to explicitly define multiple return args like uint,uint,string etc?

Let me observe your compound TokenScript in whole and decide. I don't think we can include this in May release anyway, so I'll prioritize other release showstoppers (like repo server offering action scripts)