Cobra Forums

That's right about Python not requiring parens. Though I wouldn't be opposed to requiring them outside of "return" and assignment. I'm trying to think of other places in Python where they are not required. If you want to pass them as arguments, they certainly need parens:

Code: Select all

# python
obj.foo((1, 2), (2, 1))  # 2 arguments, each a tuple of two ints
obj.foo(1, 2, 2, 1)  # 4 arguments, each an int


Btw the funny syntax that hopscc was thinking of comes into play when your tuple has only one element:

Code: Select all

# python
t = (1,)


Without a trailing comma, it would not be a tuple.

Code: Select all

# python
t = (1,)


Without a trailing comma, it would not be a tuple.

That's really ugly

(snap)
And also sorta confusing...
It may be a tuple if it has enclosing () but it doesnt always have to, sometime you need trailing commas but mostly not.
Its probably lexically convenient to tokenise/parse this way(in python) but its not very convenient for human recognition/learning/use.

I see Tuples as always useful for some things (multi-method returns with multi arg unpacking i.e ticket:315) and occasionally useful for some other things - like quick and dirty (temporary) immutable value class uses - you can do that with full blown classes but having Tuples available is faster, easier and more satisfying.

It's probably a stupid question, but couldn't tuples be something like:

variable = {'text', 14, 12.5f, DateTime.Now}
variable = function({'text', 14, 12.5f, DateTime.Now})

I'm really tired, so I'm not really thinking at this point, but it just seems like a neat use for curly braces (they need some love too), make it obvious that it's a tuple and support implicit tuples at the same time, no?

Just a thought I wanted to share before going to sleep.

Cobra already uses {} for Set {} and Dict/Map {:} literals

Whoops, totally forgot. Sorry for that

No prob - theres a lot in cobra to forget