This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-05-02
Channels
- # announcements (1)
- # babashka (4)
- # beginners (39)
- # calva (36)
- # cherry (11)
- # cider (23)
- # clj-on-windows (3)
- # clojure (105)
- # clojure-brasil (1)
- # clojure-chicago (3)
- # clojure-conj (8)
- # clojure-denver (4)
- # clojure-europe (18)
- # clojure-germany (5)
- # clojure-hungary (13)
- # clojure-nl (1)
- # clojure-norway (31)
- # clojure-sweden (9)
- # clojure-uk (2)
- # clojurescript (22)
- # core-async (4)
- # cursive (8)
- # data-science (25)
- # datomic (14)
- # devops (1)
- # emacs (9)
- # events (5)
- # holy-lambda (32)
- # hyperfiddle (26)
- # introduce-yourself (2)
- # kaocha (1)
- # leiningen (11)
- # lsp (17)
- # malli (8)
- # off-topic (84)
- # pedestal (4)
- # polylith (2)
- # re-frame (17)
- # reitit (1)
- # releases (1)
- # remote-jobs (1)
- # shadow-cljs (8)
- # sql (4)
- # tools-deps (8)
- # transit (5)
- # vim (1)
- # vscode (1)
- # xtdb (45)
Could this error be caused by the way Cursive launches the REPL? https://clojurians.slack.com/archives/C0AB48493/p1683020098221979
UPDATE: he seem to be getting the same error with lein repl
I'll continue in that #C0AB48493 thread linked above.
I had an idea regarding making the source origin of generated macros known to Cursive: what if the generating code also interfaced with Cursive somehow to let it know? As long as we are writing macros we should be able to go an extra mile and create something ti help out Cursive, or any other such tool. <= Says someone who knows nothing about how such tools work. 🙂 I am fine with a quick "search files", but I hope to lure Dart/Flutter users, who I suspect will bail without the IDE symbol recognition.
This is definitely part of my long-term plan, but it unfortunately requires undoing some very early bad decisions, so getting there is taking a long time. However, I’m planning on adding proper ClojureDart support soon, so I can add that support internally myself.
Thx for the update. FYI, I am thinking of converting a lot of the macrology to functions, out of concern over final Dart code size. The key widget macros expand into a lot of boilerplate, at least the way I did it. And in the end there will be hundreds of these, the way Flutter (and OO in general) works. Great to hear you have CLJD on your radar. I see a big future for it in the Clojure community.
Yes, I investigated it a decent amount when it first came out but then got distracted and dragged off onto other things. But I’m also excited about it so I’d like to support it well. And I think it should be possible to offer much better support than for CLJS, just because Dart is more static than JS.
Did you see the Dart 3 videos describing the new capabilities? I'm no implementation guy, but it sounds impressive. I loved individual characters being tree-shaken from fonts. I also like that they are going after speed without making devs rewrite their code. Could be the future for CLJ front-ends, and maybe CLJD can carve out a niche as a rapid-prototyping tool for Dart apps. :thinking_face: I wonder if React is keeping up?