liveBook · Manning

Library

A software library is a reusable collection of code or components that other programs can incorporate or invoke to provide functionality.

How 2 Manning books explain it

Clojure: The Essential Reference

A Clojure library is a source file whose name corresponds to the namespace declaration it contains and which follows conventions for storing and reusing Clojure code.

How it is used
Defines the file-backed unit for storing reusable Clojure code and loading it with `require`.
How deep it goes
Defines file and namespace conventions, then distinguishes library loading from namespace creation and direct file evaluation.
Examples
Uses `clojure.set` loading, a failed `require` of a fileless namespace, and warnings from referring all symbols.
What you can do after
Operate/configure it: load file-backed namespaces with `require`, inspect `loaded-libs`, and choose aliases over broad symbol imports.

Read how Clojure: The Essential Reference explains library →

Idiomatic Rust

A library is a packaged collection of reusable software components that other programs can depend on and call.

How it is used
Designs reusable Rust APIs for open-source projects, SDKs, and internal software.
How deep it goes
Explains API tradeoffs and demonstrates Cargo setup, integration testing, visibility, documentation, and maintenance practices.
Examples
Uses a linked-list crate, external integration test, public iterator types, and compiler errors about private items.
What you can do after
Build and maintain focused Rust libraries with usable APIs, external tests, correctness checks, and compatibility-conscious releases.

Read how Idiomatic Rust explains library →

Related concepts

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.