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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

A better inliner for OCaml, and why it matters

135 点作者 ch大约 9 年前

4 条评论

vegabook大约 9 年前
I love Ocaml but have ditched it for Erlang/Elixir, losing a lot of elegance on the way, but massively gaining on horizontal scalability and pragmatism. I would love to stay with Ocaml but there just isn't enough of a clear roadmap to it on multicore (seemingly fraught with controversy within the community), or even multi-node distributed computing that does not require me to reverse engineer someone's 10-year-old, badly documented thesis project. I almost feel like the Ocaml project is stuck optimizing a single-core past, and that it might be better to devise a new Ocaml-based language altogether, designed from the ground up for distributed computing. I'd be there immediately.
评论 #11170559 未加载
评论 #11172883 未加载
评论 #11170452 未加载
评论 #11170977 未加载
评论 #11172663 未加载
评论 #11170591 未加载
评论 #11172418 未加载
mwcampbell大约 9 年前
I wonder what kind of impact this will have on the performance of Mirage. It seems to me that whole-program optimization is potentially a great benefit for a unikernel written almost entirely in a high-level language like OCaml.
评论 #11171072 未加载
cm3大约 9 年前
What about dead code elimination? A simple executable using Core is >20MB.
评论 #11173733 未加载
tempodox大约 9 年前
I'm really looking forward to modular implicits. Having something like Haskell type classes is a great tool for abstraction.