This is alternative refactoring of sequence construction API. Another version is here: #480. This version uses tuples instead of elements function.
Description
Before this commit Vector functions were over-overloaded: call
to
Vector[T](a)
could interpret a as a sequence or as an element parameter. This
is over-overloading that make code harder to read and maintain.
This commit changes sequence construction API. New convention is
proposed:
Let Foo be sequence type.
Calls
Foo(arg)
Foo[T](arg)
assume arg is a sequence. Call
foo(..args)
interpret args as elements for new foo sequence. Latter call does
not work when args list is empty (because type parameter for Foo
cannot be infered and thus must be specified).
To deal with this issue, fourth constructor is added: with elements
passed in tuple:
jckarter
commented
11 years ago
What is it
This is alternative refactoring of sequence construction API. Another version is here: #480. This version uses tuples instead of
elementsfunction.Description
Before this commit
Vectorfunctions were over-overloaded: call tocould interpret
aas a sequence or as an element parameter. This is over-overloading that make code harder to read and maintain.This commit changes sequence construction API. New convention is proposed:
Let
Foobe sequence type.Calls
assume arg is a sequence. Call
interpret args as elements for new foo sequence. Latter call does not work when args list is empty (because type parameter for
Foocannot be infered and thus must be specified).To deal with this issue, fourth constructor is added: with elements passed in tuple:
This patch changes vector, queue and deque.