Build2 publishers2 min readPublished
EDG's licensed C++ front end opens to pull requests and pooled feature funding under the C++ Alliance
EDG put the C++ front end it licensed to compiler makers for 30 years on GitHub under Apache 2.0, with the C++ Alliance as its non-profit home. Toolchain teams that bought it as a closed part can now patch it in public and pay jointly for new features.
The Engineer · Build desk
What happened
- Any EDG user can send a pull request, and reviewers, initially experienced EDG developers, check each change before it is merged.
- Fixes written by EDG developers now employed by the C++ Alliance are published as soon as they are ready, without waiting for a release cycle.
- John Spicer chairs the committee that oversees the process, working alongside volunteers from the community.
- The Alliance has been Boost's fiscal sponsor since 2024 and employs engineers who contribute directly to Clang's front end in LLVM.
Compiled by The EngineerSomething wrong?How this is made
Why it matters
- decision Compiler vendors that shipped EDG under a commercial license now have to decide whether to hold fixes as private patches or send them to github.com/edgcpp/compiler, where every competitor can use them.
- constraint With maintenance fixes landing continuously in public, each downstream team has to set its own policy for which commit to pin and how often to rebase its local changes.
- capability Engineers chasing a template-parsing bug in a compiler built on EDG can read the analysis code line by line instead of treating the front end as a black box.
A C++ front end is the first stage of a compiler. It reads source code, checks it against the C++ standard and emits an intermediate representation for the optimizer and code generator [18]. EDG never sold a complete compiler. For thirty years it licensed that one stage to the companies that build them [3][8], and the dev.to account calls it the only production-quality tool of its kind on the market [7]. Most C++ programmers never heard the name, though their compilers parsed code with it [21]. The transition site concedes that EDG's own history is still to be written and asks the community to send in pieces of it [20].
Nothing inside the engine changed when the code went public on 30 September 2026, according to the dev.to account [1][22]. The account says the change is in who pays for it, who maintains it and who can read it [22]. EDG wrote on its transition site: "Same engine, same standards, professionally maintained, and open to contributions. Continuity is the point. This is a change of steward, not a change of course." [19]
The jointly funded track has one rule a toolchain budget has to plan around. All three tracks (community pull requests, maintenance and funded features) end in the same repository on the same day, and nobody receives an early version [4][14]. A group of vendors that pays for a large feature therefore pays for every vendor that did not. I think that is the right rule here. Early access for funders would rebuild a paid tier inside an Apache 2.0 codebase [16] and give the review queue two classes of customer. The cost is that features get funded by whoever cannot afford to wait for someone else to pay. The material published so far does not say how a funded feature is priced, who scopes it or how competing requests are ranked [13].
Money for that track goes to a foundation, so a funder's main check is the foundation's books. The C++ Alliance publishes financial transparency reports and has close ties to the C++ standards committees, a group that itself depends on EDG [10].
What to watch
- The first jointly funded feature: which organisations pay, what it costs, and which part of the C++ standard it covers.
- Whether review rights on the repository extend beyond EDG's original developers, and how quickly outside pull requests get merged.
- Whether vendors that licensed EDG start upstreaming their private fixes in public.