I'm trying to figure out the mechanics of process substitution fromÂ
https://www.gnu.org/software/bash/manual/html_node/Process-Substitution.htmlÂ
and the rest of the Internet.
I don't know how I'm the only Linux user who doesn't understand them despite
spending hours searching the Internet and conversing with AI chatbots, and
become so desperate that I'm asking humans for help.
The documentation implies that process substitution works much like piping in
and out of temporary files. From the little I understand, nothing could be
further from the truth. I'm struggling to figure out how asynchronous IO works,
with my first failure at the hands of JavaScript's IO. There are lots of
nuances of how a file descriptor is opened, filled, emptied and closed that I'm
discovering from error messages of "broken pipes". The documentation doesn't
seem to help.
I understand C++ and Python IO where one opens a file, reads or writes to it,
then commits the changes to disk. I can also do the same with byte streams in
memory. That paradigm seems to be working against me with process substitution.
The temporary solution I currently have is creating a mktemp directory,
stashing my information there and then wiping it in a trap. I can't seem to
figure out how I can do this in memory without involving the hard disk.
The bash manual doesn't need a lengthy explanation on asynchronous IO. It would
be sufficient to explain the differences named pipes have from stream
redirectors, generally explain how named pipes can be read and written, and
what users should search for in their foundational research.
Much obliged,