TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Cloture: Clojure in Common Lisp

129 点作者 ruricolist大约 5 年前

10 条评论

slyrus大约 5 年前
I have long desired being able to run clojure code directly in my Common Lisp environment. Interop between clojure code and CL code would be much more interesting to me than the clojure&#x2F;java interop. Yes, there&#x27;s ABCL which does the CL&#x2F;Java interop (and of course vanilla clojure has that built in), but I&#x27;m a big fan of the idea.<p>And ruricolist has written (and maintained&#x2F;forked) some nice libraries. In particular his FXML is the modern successor to cxml and plays nice with xpath, etc...
评论 #22326091 未加载
stereolambda大约 5 年前
Maybe this could lead, in a roundabout way, to saner ways of dealing with hash tables and non-list sequences in general in Common Lisp. Currently these need clunky, verbose code for many use cases. Writing your own functions&#x2F;macros is of course possible, but it feels disorganized without ensuring an overarching system of conventions. AFAIK a uniform way of handling sequences was one of the early selling points of Clojure, according to Rich Hickey himself. Sequences which are immutable, which I don&#x27;t care much for (as I cherish the out-of-your-way CL philosophy), but it&#x27;s a compromise.<p>Alternatively I could spend some time assessing rutils or some other fundamental extension library... I&#x27;d like, one day, for one of those to gain a good tutorial and a bigger mindshare in the community.
评论 #22327090 未加载
评论 #22331685 未加载
classified大约 5 年前
I propose naming it &quot;Clôture&quot;, for clarity.
Scarbutt大约 5 年前
I can understand escaping from Java enterprise hell to Clojure but devs using a CL runtime will just write CL?
评论 #22324784 未加载
评论 #22324563 未加载
评论 #22323932 未加载
评论 #22326100 未加载
评论 #22323960 未加载
评论 #22325329 未加载
评论 #22325539 未加载
lbj大约 5 年前
&gt; &quot;Beside the obvious: cloture is a parliamentary procedure to end debate on a subject, and I would like to end certain debates. Yes, Common Lisp is “modern.” Yes, Clojure is a Lisp.&quot;<p>Im interested to see how well this will fare. Personally, Im a little depressed that Clojure-in-Clojure has been postponed for nearly a decade. It would have made changing compiler targets much easier.
e12e大约 5 年前
&gt; Clojure namespaces are just packages. But of course Clojure is case sensitive, so you will need to use pipe characters to call, for example, |clojure.core|:|cons|.<p>Is this an implementation detail or a common lisp idiom to work with case (in)sensitivity?
评论 #22325321 未加载
globular-toast大约 5 年前
Can&#x27;t wait to have a go with this. Common Lisp is a joy to work with but I would actually prefer to use Clojure because I like functional programming. But while I tried to get into Clojure I just hate having to run the JVM and having Java interop is worthless to me. So being able to use the Clojure functionality in a more familiar environment might be perfect.
评论 #22325573 未加载
cellularmitosis大约 5 年前
Don&#x27;t some Common Lisp implementations support heap snapshots? Might improve Clojure startup time.
评论 #22326394 未加载
评论 #22324990 未加载
voldacar大约 5 年前
Cloture and Clojure, not to be confused with Clozure
评论 #22324412 未加载
评论 #22329531 未加载
ScottBurson大约 5 年前
Glad you&#x27;ve found FSet useful! I&#x27;m curious what the difference is in map equality semantics.