Deterministic behavior in list types like Vector

[jcalfee]

To provide deterministic behavior in transactions, which Vectors should be sorted? Probably almost all vectors need sorting except for the Message vector.

Because this type is both dynamic in contracts and really changes the meaning of the data type, I think it is better to have the user say when to sort (instead of sorting by default). Like this:

struct Transaction
   refBlockNum       UInt16
   refBlockPrefix    UInt32
   expiration        Time
   scope             AccountName[](sort=true) # the data may be accessed while processing this transaction
   messages          Message[]

[bytemaster]

Interesting idea, perhaps AccountName[ordered] or AccountName[sort] would achieve the same goal?

[jcalfee]

Looks good, unless you need some other type parameter later.

Lets consider these equal:

Vector[AccountName] == AccountName[]

A hypothetical example might be the Set:

Set[Table](unique=table)

[jcalfee]

Guess you could use another symbol for that: Table{unique=table} .. Going that route use your better looking syntax: AccountName[sort] ..

[bytemaster]

Also support for fixed size arrays.

[jcalfee]

How about basic uri processing and encoding decoding (if needed) rules:
AccountName[20] or AccountName[length=20&sort]

Do you think it would be safe to turn Vector sorting on my default? The exact opposite of what I said above (lol). I know of only one case to not sort:

struct Transaction
   refBlockNum       UInt16
   refBlockPrefix    UInt32
   expiration        Time
   scope             AccountName[]   # the data may be accessed while processing this transaction
   readscope         AccountName[]   
   messages          Message[sort=false]

[jcalfee]

Consider non-array types would need a parameter delimiter. I'll use a hypothetical Set example. That would be uri like too. If you want to scrape this usage (AccountName[length=20&sort=false]) we will have something consistent:

Set?unique=name // other element
AccountName[20]?sort=false // sorted unless specified otherwise

[andriantolie]

We don't have scope anymore. I'm going to close this issue