I/O
Input/output is the transfer of data between a program or system and external sources or destinations, such as files, devices, services, or networks.
Functional Programming in C#, Second Edition
Input/output (I/O) comprises operations through which a program reads or writes data in communication with external resources or systems.
- How it is used
- Explains why programs need I/O and how to isolate it from pure computation.
- How deep it goes
- Defines I/O as external interaction and works through isolation and clock-dependent validation, without detailing a complete I/O abstraction.
- Examples
- Uses console input and output, document conversion, URL and file operations, and clock-dependent transfer validation.
- What you can do after
- Apply functional design by isolating I/O from pure computation and recognizing clock-dependent validation as impure.
Read how Functional Programming in C#, Second Edition explains I/O →
Python Concurrency with asyncio
An I/O operation transfers data between a program and an external resource such as a file, device, or network endpoint.
- How it is used
- Frames I/O as the main source of application blocking and motivates concurrency for responsive programs.
- How deep it goes
- Explains blocking, concurrency, and GIL release during I/O, but stops short of detailed system-call mechanics.
- Examples
- Uses keyboards, hard drives, network cards, web APIs, and repeated example.com status-code requests.
- What you can do after
- Apply concurrency with asyncio or threads to overlap waiting web requests and improve responsiveness.
F# in Action: A Revised Edition of Get Programming with F#
External I/O is input or output involving a resource outside the program, such as a network service or database.
- How it is used
- Uses I/O to organize interactions with HTTP, databases, files, consoles, and other external resources.
- How deep it goes
- Explains boundary placement and asynchronous use cases, but stops short of implementation details or type-level enforcement.
- Examples
- Uses HTTP requests, database calls, console interaction, file systems, JSON validation, SQL commands, and HTTP responses.
- What you can do after
- Apply it via boundary-oriented design that keeps business logic pure and makes asynchronous external work explicit.
Read how F# in Action: A Revised Edition of Get Programming with F# explains I/O →
The Quick Python Book, Fourth Edition
I/O is the transfer of data into and out of a program through streams, files, devices, or other interfaces.
- How it is used
- Handles interactive input, terminal streams, file redirection, text and binary files, and persistent Python data.
- How deep it goes
- Explains input conversion, stream methods, redirection and restoration, then points to specialized persistence and binary-format tools.
- Examples
- Demonstrates input(), integer conversion, sys.stdin.readline(), stdout redirection, print(file=f), and captured file contents.
- What you can do after
- Apply Python’s input, stream, file, path, binary-format, and persistence interfaces to move or save program data.
Read how The Quick Python Book, Fourth Edition explains I/O →
Code Like a Pro in Rust
I/O is the exchange of data between a program and an external source or destination such as a file, device, or network.
- How it is used
- Frames I/O as a stateful operation requiring error handling, testing, and an execution model suited to waiting time.
- How deep it goes
- Explains blocking and nonblocking behavior, waiting-time interleaving, and testing implications without detailing specific APIs.
- Examples
- Uses filesystem access, sockets, timers, hash computation, and a blocking-versus-nonblocking timing figure.
- What you can do after
- Evaluate whether synchronous blocking or asynchronous nonblocking I/O better fits waiting-heavy workloads and test I/O paths appropriately.
Systems Programming with Zig
Input/output is the transfer of data between a program and external devices, files, networks, or other processes.
- How it is used
- Connects a simple printing program to practical choices about buffering, flushing, and I/O interfaces.
- How deep it goes
- Traces writer setup, buffered printing, and flushing; mentions io_uring without implementing it.
- Examples
- Prints a greeting to standard output with a buffered writer and explicit flush.
- What you can do after
- Apply std.Io to write and flush output through a buffered writer.
Also covered in
- Learn Haskell by Example
- Learn Concurrent Programming with Go
- Quarkus in Action
- Modern C, Third Edition
- Data-Oriented Programming in JavaIn early access (MEAP)
- Fast Python: High performance techniques for large datasets
- The Well-Grounded Rubyist, Fourth Edition
- Grokking Concurrency
- JavaScript in DepthIn early access (MEAP)
- Rust in Action: Systems programming concepts and techniques
- Troubleshooting Java, Second Edition
- Modern C
What to know first
- pure functionA pure function is a function whose result depends only on its explicit inputs and whose evaluation has no externally observable side effects.
- workflowA workflow is an organized sequence of coordinated activities or tasks through which work progresses toward a defined outcome.
- CPUA central processing unit (CPU) is a computer processor that executes program instructions and performs general-purpose computational operations.
- HaskellHaskell is a statically typed, purely functional general-purpose programming language with non-strict, typically lazy evaluation.
Related concepts
- asynchronous programmingused by · Asynchronous programming structures operations so that the initiating execution can continue or yield control without synchronously waiting for each operation to complete.
- file descriptoruses · A file descriptor is an operating-system identifier for an open file, socket, pipe, or other input-output resource.
- clojure.java.ioused by · clojure.java.io is a Clojure namespace that provides polymorphic utilities for interacting with Java input/output resources, files, URLs, and classpath resources.
- distributed systemused by · A distributed system is a computing system whose components run across multiple networked processes or machines and coordinate through communication.
- impure functionused by · An impure function is a function whose result depends on external state or whose evaluation produces observable effects beyond its returned value.
Questions about I/O
What is I/O?
Input/output is the transfer of data between a program or system and external sources or destinations, such as files, devices, services, or networks.
Which Manning books explain I/O?
Functional Programming in C#, Second Edition, Python Concurrency with asyncio, F# in Action: A Revised Edition of Get Programming with F#, The Quick Python Book, Fourth Edition, Code Like a Pro in Rust and Systems Programming with Zig.
What should I know before learning I/O?
Manning books that teach I/O usually introduce pure function, workflow, CPU and Haskell first.
What kinds of I/O are there?
Kinds of I/O include blocking I/O.
What is I/O also called?
I/O is also called input/output, input and output or IO.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.





