News for hackers. Stuff that matters.
Re:Swift for TensorFlow Shuts Down by renox on Friday February 12, 2021 @08:41PM (#26120697)
Sigh, <> isn't the only way, D (as usual) has a very simple and clever solution f!(types)(parameter)
Re:Swift for TensorFlow Shuts Down by eigenspace on Friday February 12, 2021 @08:57PM (#26120772)
Maybe it's just my julia indoctrination speaking but I find that rather ugly.

In julia, f!(types)(parameter) means that f! is a mutating function acting on types which returns a closure which is then called on parameter.

We just write Type{paramemer}

Re:Swift for TensorFlow Shuts Down by jodrellblank on Saturday February 13, 2021 @03:59PM (#26126838)
> "We just write Type{paramemer}"

It seems odd to say "we just write" for some arbitrary choice with its own tradeoffs; {} mean a set in Python or a literal array initialiser in C# or a scriptblock in PowerShell or a dfn in Dyalog APL or a JSON dictionary, etc. With only a limited set of whatever symbols happened to end up on a US ASCII keyboard 40+ years ago, there is heavy competition for them, it's why J broke the symmetry of pairs and went for two-character symbols, why PowerShell went for comparators like -gt and -lt, why C# has => which is completely different from <=, why << is not a double application of less-than but is bit shifting ...

To act like there's an objectively better use for {} is to miss how many tradeoffs there are, and how many things people want symbols for out of a standard keyboard.

Re:Swift for TensorFlow Shuts Down by eigenspace on Sunday February 14, 2021 @02:21AM (#26130363)
I never said it was objectively better.

My point was just that we find Type{parameter} to be nice pleasing syntax, and so reserved the curly braces for that.

Of course it’s not objectively better, that’s a dumb attitude towards syntax.