to follow up https://clojurians.slack.com/archives/CPABC1H61/p1791400371925029 in #CPABC1H61, i'm trying my hand at making rewrite-clj much more lax in how it reads invalid code, to make it possible to "fix" broken code when it appears. i know there's a https://github.com/clj-commons/rewrite-clj/issues/87 with a bunch of discussion over the last decade about this, but i don't see any actionable code examples, so i thought i might try my hand at it. is thing something y'all are interested in? would we want to gate it behind a dynvar or feature flag or something? rewrite-clj's internals don't use an opts map like edamame, so it's hard to simply say (if (:lax opts) (lax-read-token ...) (edn/read-token ...)) etc
i wrote up potential solutions in the github issue, and then i put up a draft PR to help facilitate the discussion discussion: https://github.com/clj-commons/rewrite-clj/pull/489
(i know the previous message is about me doing something else to rewrite-clj lol, i have a lot of active branches)