Problem 8: Create Go channels… without Go channels

[mpldr]

This one is a bit different:
We want a channel implementation at least similar to channels in Go. Unbuffered channels to be more precise.

A short rundown:

• a channel can "transport" any type
• a channel write is blocking until the value is consumed
• similarly a read is blocking until a value is received
• channels can be reused

The solution being stable, secure, or sensible is not part of the problem.

[mpldr]

I fear this one might actually be useful… but hey, even a blind hen sometimes finds a grain of corn.

[mpldr]

https://github.com/Ta180m/Idiot-Code-Golf/blob/main/channels/bashnels.sh

Is it tested? only for the most basic of use-cases.
Is it working? surprisingly: yes
Is it stable? depends on your definition of stable.

[ghost]

https://github.com/Ta180m/Idiot-Code-Golf/blob/main/channels/channels.cpp

A "modern C++" solution by hacking together some C++ 17 and C++ 20 features such as std::any, auto, and concepts. std::any in particular feels like such a crazy hack of a language that has deviated so much from C by trying to do everything possible. Obviously, this a naïve implementation that should not be used if you're actually working with concurrency. Among the many flaws, reads will consume 100% CPU in the while loop until it receives a value.

[mpldr]

reads will consume 100% CPU in the while loop

That's just a free bonus :D

I haven't tried it yet, but does it block on write? because then it should not be able to run… or better: finish