🚀 go-pugleaf

   There are occasions where largish files get written to disk and t
then read right back in again.  System builds, for example, write .o files
and then read them back.  (Does NeXT write intermediate files, too?)

   In such a case, a way to write data to a "file" that stays in memory
seems useful.  Normal cacheing doesn't accomplish it, since the files
get synced to disk pretty often.

   Of course, IF the "files" in memory contend for memory, they should be
swapped out, just like any other memory contender.  But if there is
lots of memory free, they would stay in memory and thus speed up system
building.

      In short, there should be a way to create memory resident files
which aren't synced to disk unless absolutely called for.