This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-01-28
Channels
- # asami (5)
- # babashka (44)
- # beginners (22)
- # biff (7)
- # clerk (86)
- # clj-kondo (5)
- # clojure (33)
- # clojure-europe (8)
- # clr (6)
- # community-development (2)
- # fulcro (20)
- # graalvm (5)
- # graphql (1)
- # hugsql (3)
- # integrant (5)
- # java (11)
- # joyride (2)
- # leiningen (4)
- # malli (12)
- # nbb (15)
- # off-topic (28)
- # pathom (23)
- # reitit (8)
- # releases (1)
- # sci (6)
- # shadow-cljs (39)
- # tools-deps (15)
- # tree-sitter (1)
Two new posts on the ClojureClr.Next blog: https://dmiller.github.io/clojure-clr-next/general/2023/01/27/doing-a-number.html https://dmiller.github.io/clojure-clr-next/general/2023/01/27/first-code.html Yes, we have code.
Very exciting progress! Great work, @U45FQSBF1!
This time around let's transform the clojure.core source into portable Clojure with .cljc, .cljr and *.clj files cleanly separated (such that when compiling with mainline clj, all tests pass for JVM, too). Yes, I volunteer to work on that, since I brought it up. 🙂 You did make it a bit easier by commenting everywhere you made a change to the original clj file.
The only hesitation I have is maintenance. Right now core.clj and most of the other Clojure source files are line# equivalent. If there is a commit in the JVM version on line 3178 of core.clj, I can go right to line 3178 in my copy and make the change. I should probably just over that. It would make a huge difference for things like editing the comments properly, which I do not do.
I did consider it. Several reasons I didn't go that way. One is the whole bootstrapping issue -- you need a clojure to bootstrap your new clojure implementation. Another is that I figure doing in Clojure-in-Clojure is above my pay grade. That's a Rich project. And I wanted to learn F#. 🙂