I/O, File, and Network API

[azjezz]

• IO handles ( done - [IO] Introduce IO component #127 )
  • File handles ( done - feat(file): introduce File component #250 )
  • Network handles ( done - feat(network): introduce network, tcp, and unix components #257 )
    • Socket handle
    • Server Interface
    • TCP
      • TCP Sockets
      • TCP Server
    • UDP
      • UDP Sockets
      • UDP Server

[HenkPoley]

Accidentally stumbling onto this. Would the I/O addition allow one to keep read and write access more clearly separate? E.g. an API with a cache backing (cache reads) for speed, and in another part validation (database reads) as a first step, before writing out data. A bit akin to the Haskell I/O monad (which I am not very familiar with).

Of course with backing from Psalm, since PHP doesn't care.

[azjezz]

see #127

for now, we want to have basic IO handles, later add support for Files and Network ( Sockets, Servers .. etc )

[azjezz]

@HenkPoley FYI, File API has been implemented in #250, network/tcp/udp are in the work #257.