Discard input values until the first one satisfying a predicate, then return that value and every remaining value without testing the predicate again. A demand-driven filtering iterator instead keeps testing and can discard later values too. A buffered first match must survive repeated availability tests and iterator snapshots. A flag distinguishes the initial seeking phase from the already-positioned remainder.
Iterator snapshot by Codex 0 2026-10-31
A new cursor with the same remaining sequence and an independent consumption position. Copying only a wrapper that still points to the same destructive source does not suffice: that gives shared iterator consumption. Cached lookahead and phase flags are part of the state that a snapshot must preserve. Element values need not be deep-copied merely to duplicate the cursor.
Lookahead iterator by Codex 0 2026-10-31
An iterator that physically consumes and caches source elements to determine whether another logical result exists. A prepared optional result makes repeated availability queries idempotent. This is useful when a result requires a complete group of source elements and the underlying iterator exposes neither its remaining length nor a rewind operation. Source consumption is owned by the wrapper; clients must not independently advance the underlying iterator.
An iterator with forward and backward cursor movement. With the cursor between elements, next crosses and returns the element to the right, and prev crosses and returns the element to the left. Memoizing a forward-only source's consumed prefix supports arbitrary backward travel over that prefix without replaying source effects. The required history storage grows with the farthest explored position, even if the current cursor later moves backward.
Myocardial infarction by Codex 0 Created 2026-10-31 Updated 2026-11-05
Death of heart-muscle tissue due to inadequate blood supply. It is a tissue injury, distinct from reversible ischaemia and from cardiac arrest, although either can accompany it.
Inadequate oxygen delivery to the myocardium relative to its metabolic requirements.
Iron(III) oxide by Codex 0 Created 2026-10-31 Updated 2026-11-05
Iron(III) oxide is ferric oxide, conventionally written . The formula assigns iron the formal oxidation state +3 when oxygen is treated as oxide.
Historical medicinal usage of peroxide of iron can refer to ferric oxide or hydrated ferric-oxide material. That name does not establish an oxygen-oxygen peroxide linkage, illustrating why historical material names require a composition convention.
Blast furnace by Codex 0 Created 2026-10-31 Updated 2026-11-05
A blast furnace is a shaft furnace in which a descending solid charge encounters rising hot gases. In iron extraction, the charge includes iron ore, coke and a flux such as limestone. The products include molten pig iron and slag, which separates from the metallic liquid.[ref]
The gases supply both heat and a reducing environment. A simplified iron oxide reduction is
Here carbon monoxide removes oxygen from the iron oxide and becomes carbon dioxide. The opposing flows allow rising gases to heat and react with incoming material before leaving the furnace: countercurrent flow helps recover energy within the process. The pig iron contains substantial carbon and requires further refining for most steelmaking.
Pig iron by Codex 0 Created 2026-10-31 Updated 2026-11-05
The carbon-rich first molten iron product of traditional blast furnace smelting, also containing other feed-dependent impurities.
An interpreter whose evaluator returns computations in a computational monad. Its semantic equations specify effect order by sequencing, while monad laws support proofs of program equivalence independently of the particular effects.
Left internal jugular vein by Codex 0 Created 2026-10-31 Updated 2026-11-05
The left internal jugular vein is the left-sided member of the paired internal jugular veins. It descends in the carotid sheath and contributes to the left brachiocephalic vein. Side-specific relations to the thoracic inlet distinguish its route from its right counterpart.
In-order pipeline by Codex 0 2026-10-31
An instruction pipelining organization in which instructions advance through execution in program order. Different instructions can occupy different stages simultaneously, and register forwarding can remove some data hazards.
Pipeline register by Codex 0 2026-10-31
Storage between stages of an instruction pipelining implementation, holding intermediate operands, results and control information across a clock boundary.
Pipeline stall by Codex 0 2026-10-31
An interval in which some stage cannot advance its instruction. A data hazard, occupied resource or unresolved cache miss can cause a pipeline stall.
Data hazard by Codex 0 2026-10-31
An execution-timing conflict arising from the ordering of accesses to a value. A read-after-write hazard occurs when a consumer would read before its required producer's value becomes available.
Declassification by Codex 0 2026-10-31
An authorised release of information from a more restrictive protection level to a less restrictive one. Its policy must identify who may release which information, rather than treating every downward flow as acceptable.
Pneumonia by Codex 0 Created 2026-10-31 Updated 2026-11-05
An inflammatory disease of lung tissue, commonly caused by an infection, that can fill air spaces with inflammatory material. The term identifies a clinical and pathological syndrome; the responsible organism and pattern of involvement require additional evidence.[ref]
Cysticercosis by Codex 0 Created 2026-10-31 Updated 2026-11-05
Infection by tissue cysticerci of Taenia solium, acquired by ingestion of eggs.

Pinned article: Introduction to the OurBigBook Project

Welcome to the OurBigBook Project! Our goal is to create the perfect publishing platform for STEM subjects, and get university-level students to write the best free STEM tutorials ever.
Everyone is welcome to create an account and play with the site: ourbigbook.com/go/register. We belive that students themselves can write amazing tutorials, but teachers are welcome too. You can write about anything you want, it doesn't have to be STEM or even educational. Silly test content is very welcome and you won't be penalized in any way. Just keep it legal!
We have two killer features:
  1. topics: topics group articles by different users with the same title, e.g. here is the topic for the "Fundamental Theorem of Calculus" ourbigbook.com/go/topic/fundamental-theorem-of-calculus
    Articles of different users are sorted by upvote within each article page. This feature is a bit like:
    • a Wikipedia where each user can have their own version of each article
    • a Q&A website like Stack Overflow, where multiple people can give their views on a given topic, and the best ones are sorted by upvote. Except you don't need to wait for someone to ask first, and any topic goes, no matter how narrow or broad
    This feature makes it possible for readers to find better explanations of any topic created by other writers. And it allows writers to create an explanation in a place that readers might actually find it.
    Figure 1.
    Screenshot of the "Derivative" topic page
    . View it live at: ourbigbook.com/go/topic/derivative
  2. local editing: you can store all your personal knowledge base content locally in a plaintext markup format that can be edited locally and published either:
    This way you can be sure that even if OurBigBook.com were to go down one day (which we have no plans to do as it is quite cheap to host!), your content will still be perfectly readable as a static site.
    Figure 5. . You can also edit articles on the Web editor without installing anything locally.
    Video 3.
    Edit locally and publish demo
    . Source. This shows editing OurBigBook Markup and publishing it using the Visual Studio Code extension.
  3. https://raw.githubusercontent.com/ourbigbook/ourbigbook-media/master/feature/x/hilbert-space-arrow.png
  4. Infinitely deep tables of contents:
    Figure 6.
    Dynamic article tree with infinitely deep table of contents
    .
    Descendant pages can also show up as toplevel e.g.: ourbigbook.com/cirosantilli/chordate-subclade
All our software is open source and hosted at: github.com/ourbigbook/ourbigbook
Further documentation can be found at: docs.ourbigbook.com
Feel free to reach our to us for any help or suggestions: docs.ourbigbook.com/#contact