autothreading

They really need to remove autothreading and replace it with a dedicated media type for long form text.

Functional programming primitives include currying, lazy and eager list evaluation, junctions, autothreading and hyperoperators (vector operators).

Functional programming primitives, lazy and eager list evaluation, junctions, autothreading and hyperoperators (vector operators) 3.

The autothreading feature is cool but also nothing too special.

Automation with autothreading would definitely be a nice feature.

- Roles (OO programming) - Junctions, autothreading and hyperoperators (functional programming).

I can think of grammars, junctions, autothreading.

In fact the intuitive read is correct: if all(ar1) < any(ar2) # if all in ar1 are numerically less than any in ar2 > The autothreading feature is cool To be clear, the whole point of junctions is autothreading; passing junctions to any code that does not have an overload for junctional arguments is automatically (semantically, at least) data parallelized and that's the win that makes them significant.

In certain instances, they can look like a feature you know, but they're more generalized than any of those: sum types, switch statements with multiple cases, combined guards, sets… Autothreading gives the ability to automatically parallelize certain constructs (for instance, when an expensive operation happens on a junction).

Autothreading and hyperoperators are a cool sounding way to parallelize stuff, but getting good parallel performance is complex and counterintuitive.