Trim roadmap to forward-looking work, close #85, bump to v0.2.0 - #111
Merged
Merged
Conversation
Removes the completed v1-v3.14 historical narrative (now covered by git history and closed GitHub issues) and drops issue references that have since been closed. Keeps only the still-open gaps, issue #85 (the sole remaining open issue), and the existing v4/Future roadmap sections. Investigated issue #85 (arity-mismatch/file-not-found diagnostic wording parity with OpenSCAD): not an easy fix. It requires porting a large chunk of OpenSCAD's per-builtin diagnostic message catalog and threading a diagnostics sink through Interpreter::evaluate, which has none today. Left open per the issue's own recommendation to defer until wording parity becomes an actual requirement.
Closed as won't-fix on GitHub (cosmetic diagnostic-wording gap, not worth the cost of porting OpenSCAD's message catalog). No open issues remain, so the roadmap status note no longer needs to point at one.
README's language-completeness narrative was actively stale: it listed dot-member access, function-literal call results, arg ordering, and Unicode-string edge cases as "confirmed-but-still-open gaps," but all of those were fixed and closed (issues #79-#82) since that text was written. Rewrote both README sections to describe current state without pinning to specific roadmap version headers (v3.7/v3.8/etc.) that no longer exist in the trimmed roadmap.md. Also dropped a similar stale version citation in architecture.md.
Filed #108 (multi-variable/C-style/nested for in list comprehensions), #109 (assert()/echo() as chainable expressions), and #110 (extend corpus validation past 3D/features) — all labeled enhancement + help wanted, #110 also good-first-issue since the tooling for it already exists. roof(), textmetrics()/fontmetrics(), and linear_extrude's segments= were deliberately left untracked: real gaps, but low real-world value (roof() is still experimental upstream, the others are rarely-used power-user knobs) — same reasoning as closing #85 as won't-fix rather than carrying low-value tracking debt forever. Removed the roadmap's "Known gaps" section now that its contents live as issues, and updated README's two references accordingly.
Substantial work has landed since v0.1.0's "Early release" tag: the July 2026 correctness audit's 33 issues plus a full corpus-validation cycle against real OpenSCAD (issues #28-#110), all closed. Bumping the in-source version (CMakeLists.txt project(VERSION), vcpkg.json) so CHISELCAD_VERSION (shown in-app) matches whatever gets tagged/released, rather than a v0.2.0 GitHub Release shipping binaries that still self-report v0.1.0. Also adds a README "Download" section pointing at the Releases page for users who don't want to build from source — release.yml already builds and attaches Windows/Linux x64 archives to every version tag, but nothing in the README told users that page exists.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Interpreter(which has none today). Closed as not-planned rather than carried as low-value tracking debt.docs/roadmap.mdfrom ~1000 lines to ~30: removed the completed v1–v3.14 changelog-style narrative (now covered by git history and closed issues) and dropped references to issues that have since closed. Kept only the still-open v4/Future roadmap sections.enhancement+help wanted:forclauses #108 — list comprehensions don't support multi-variable/C-style/nestedforclausesassert()/echo()not supported as chainable expressions #109 —assert()/echo()not supported as chainable expressions3D/features(alsogood first issue)roof(),textmetrics()/fontmetrics(), andlinear_extrude'ssegments=were deliberately left untracked — real but low real-world-value gaps, same reasoning as closing [Low] Missing arity-mismatch / file-not-found diagnostic wording parity with OpenSCAD (cosmetic) #85.)docs/architecture.mdtext that had gone stale relative to current reality (listed several already-fixed issues as "still open," and referenced roadmap version headers that no longer exist).CMakeLists.txt,vcpkg.json) from 0.1.0 → 0.2.0 to match the substantial work landed since the v0.1.0 "Early release" tag (the full correctness-audit + corpus-validation cycle, issues [Critical]&&/||never short-circuit — both operands always eagerly evaluated #28–[Low] Extend OpenSCAD corpus validation beyond 3D/features #110) — so av0.2.0release tag doesn't ship binaries whose in-app version string still says 0.1.0.release.ymlalready builds and attaches Windows/Linux x64 binaries per tag but the README never mentioned it.Test plan
CMakeLists.txt'sproject(VERSION ...),vcpkg.json's"version") — no source/behavior changes.ci.yml) will build and run the existing test suite on this PR as usual.v0.2.0yet — the release workflow's own convention is to tagmainafter merge, not a feature branch.Generated by Claude Code