Skip to content

History / Solving the Multicore Dilemma

Revisions

  • Solving the Multicore Dilemma: queue sizes and loop-carried state, speculation and dead code, the timeout on main, the recomputation example, measured switch sizes, hardware synthesis; same hardware note on Motivations

    @lukehutch lukehutch committed Nov 20, 2026
  • Motivations: everything is a morphism, the algebra under the syntax, what the checker proves on every build; present tense on both pages; a code example in every section; corrections from review against the language definition

    @lukehutch lukehutch committed Nov 20, 2026
  • Reorder Motivations by impact and novelty, reword the pages in plainer prose Motivations: sections now run from the ideas that matter most to everyday programming, and are newest, to the more specialized ones; the Contents list and intro follow the new order. Each section opens with the problem it solves. Solving the Multicore Dilemma: reworded in the same order; the Related section is removed; quotation marks around phrases taken from the Spark, Flink, Beam and TensorFlow documentation, and around "now" and "current value", are removed and the phrases reworded. Code lines wrapped to at most 112 characters. Home reworded.

    @lukehutch lukehutch committed Nov 20, 2026
  • Correct claims that the design does not support: units, the order facet, loop storage, grammar round trips, build-time evaluation, C pointers, unproved laws, memo arenas, stepping backward

    @lukehutch lukehutch committed Nov 20, 2026
  • Move the dependency-graph writeup to Solving the Multicore Dilemma; summarize the other features on Motivations; link both from Home

    @lukehutch lukehutch committed Nov 20, 2026