There are vram disks, so at least you can use it for the swap.
18 karma · joined February 21, 2016
https://itunes.apple.com/us/app/foobar2000/id1072807669?mt=8
But as to the single feature you mentioned, see for example Code Bubbles:
Not just it would be harder, but you couldn't get into space without it at all, so that got comparatively easier.
Is it still all easy, though?
Paraphrasing the joke about new standards: we had a problem, so we created a beatiful abstraction. Now we have more problems. One of the new problem being normalization.
It doesn't undermine the good that Unicode brought, but you can't say to have included some unilib.h and use its functions without understanding all the Unicode quirks and its encodings, because some of the parameters wouldn't even make sense to you, like the same normalization forms.
https://eev.ee/blog/2015/09/12/dark-corners-of-unicode/
But one's sticking with only some part of Unicode support that they understand/need is easy, sure.
http://www.lmdb.tech/doc/group__mdb__env.html#ga492952277c48...
Ctrl+f through the doc for "MDB_FIXEDMAP" for more details.
So there is _some_ support, where you can expect to have the whole file at a fixed address. What is not handled is that your data may be moved within the file, and there's nothing you can do about it, short of keeping a long-lived read only transaction:
https://symas.com/lightning-memory-mapped-database/
Except, it allows only a single writer and it's not directly byte-addressable, unless you make a request to preallocate a chunk of fixed-size mmap'ed memory.
- gcc5 definition: https://github.com/NixOS/nixpkgs/blob/master/pkgs/top-level/...
- Old cc wrapper with a custom libc option https://github.com/NixOS/nixpkgs/blob/master/pkgs/top-level/...
- libc in the GCC package itself: https://github.com/NixOS/nixpkgs/blob/master/pkgs/developmen...
The whole system is very modular and customizable. But yeah, very hackish and undocumented.