Gleam 1.0 module privacy: choosing the export boundary when pub is the only modifier
Gleam 1.x treats every top-level function as private unless it carries the pub keyword. Code written against earlier releases that relied on implicit cross-module access therefore sits on a compatibility boundary: source that compiled before now needs an explicit export decision for each function another module calls. That decision is straightforward for a l
gleam