okay but the author has to write it, why not write something useful open source?

Don’t like it one bit

If bash is hard to program, get away with it, not build atop of it.

Gotta read the paper, this is a game-changer.

it is for advanced users

I came up with “composite”.

If people would accept “category”… I mean, we could also have accepted anything, except the new one can express its semantics.

Think two things:

1. optimize the control flow of your code

2. make it easy to read

You should also be disciplined with these two ideas, your code will look better as you become more experienced, 100% guaranteed.

codidact is open source, otherwise very similar to stackoverflow.

He introduces but also criticizes the use of call/cc, 1. not being a function and looks like a function, 2. able to produce an union of types with it.

Is he correct? What do you think?

This question is quite specific to Go, also specific to the algorithm you using. You should also ask on the Go mailing list, or benchmark your algo in Go and then ask on rust mailing list.