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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

Learn Chapel in Y minutes

24 点作者 ianbertolacci将近 10 年前

3 条评论

ianbertolacci将近 10 年前
I was disappointed at the lack of really good, in depth Chapel tutorials that weren&#x27;t also the spec, so I wrote my own. Looking for feedback on what could make this a better read.<p>Full disclosure: I am currently an intern with the Chapel team at Cray, and I am no shame trying to sell this open source language to the masses. However this is not a product of the internship; one can get surprisingly bored in Seattle, and I wrote this on unoccupied weekends.
评论 #10029875 未加载
kwhitefoot将近 10 年前
&gt;What this tutorial is lacking:<p>Any hints about what makes Chapel special and useful. A short section with links to relevant parts of the full documentation that highlights what one might use Chapel for. I saw some nice features but nothing that really struck me as decisive.<p>As gberger says, that should go at the top of the page.
评论 #10030255 未加载
评论 #10030551 未加载
评论 #10030164 未加载
kwhitefoot将近 10 年前
&#x2F;&#x2F; We can also enforce a form of polymorphism with the &#x27;where&#x27; clause &#x2F;&#x2F; This allows the compiler to decide which function to use. &#x2F;&#x2F; Note: that means that all information needs to be known at compile-time. &#x2F;&#x2F; The param modifier on the arg is used to enforce this constraint.<p>This sounds like it means that I cannot supply a variable as the argument to whereProc. Is that correct?
评论 #10031495 未加载