Depends on how narrow you want to make your definitions of 'language'. If a library can handle things ergonomically and fast, no need to bake it into the language itself.
Eg Perl has regular expressions built in, but Python handles them via a library (arguably it's via the standard library).
What languages can we cite that have a stdlib that doesnt include either file io, network io (or if I really want to make the point: syscalls)?
I can go first actually, get one answer out of the way. Javascript. But it did evolve network io, and modern JS runtimes almost all include some file/storage io.
Im down with a big-language/small-language discussion, but it seems basically beside the point here. I said language, but whether it's the language or libraries doesn't seem materially interesting useful or to alter the basic lay of the discussion of what consuming io-uring may well be like for most (likely: abstracted).
Depends on how narrow you want to make your definitions of 'language'. If a library can handle things ergonomically and fast, no need to bake it into the language itself.
Eg Perl has regular expressions built in, but Python handles them via a library (arguably it's via the standard library).
More drastically: C has a few loops built in, and Haskell handles arbitrary loops via a library and you can build your own new constructs, too. See https://hackage.haskell.org/package/monad-loops-0.4.3/docs/C...
(Incidentally, that's why Haskell is one of the best imperative languages.)