Tcl on steroids (i.e. merge between Tcl and REBOL)
まだ誰も着手していません。
評価
調査の方向性
The issue names no files, tests, or entry points. Start by reviewing the repository's current interpreter structure and the proposed Tcl/AST direction; done would require an agreed concrete scope and acceptance criteria before implementation can begin.
索引モデルが issue の本文から書いたものです。
説明
I like Tcl a lot and would want to have it more widespread. The only thing which I find rather unfortunate is that Tcl treats everything as string by default.
This property has one side-effect - the amount of generic optimization (i.e. not by implementing some commands in native code instead of Tcl itself) has a limit which is unfortunately quite low considering current HW (even "embedded" one).
After I read your blog post https://zserge.com/posts/tcl-interpreter/ where you @zserge encourage readers to come over here with contributions I decided to express an idea I have in my head for quite some time already.
I envision a Tcl-like language which doesn't build upon strings, but directly AST (abstract syntax tree). The ideal is merging Tcl with REBOL. Why not REBOL directly? Because REBOL (and its current successor Red) tries to get it to an extreme leading to some very very opinionated (in contrast to practical & fair-minded) decisions.
There is also Spry trying to get away from those opinionated decisions of REBOL/Red, but it lacks development force for many years 😢 (and thus suffers from some long-standing issues as well as the "missing delimiter issue" (where all functions/methods/commands/... have always fixed number of arguments which one has to remember because there is nothing like a delimiter in the language at all)).
I actually think that one could make "something like Spry", but even smaller by merging in some cool ideas from Tcl languages. Using some clever mutable tree structure which is cache oblivious could make such language really fast (currently the state of the art seems to be MinWEP ; naive pointer-based trees or the good old B-trees are by far insufficient nowadays and here is why).
Thoughts?
- 主要言語
- C
- スター
- 528
- フォーク
- 64
- PR マージ指標
- 30日以内にマージされた PR はありません
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
zserge/partcl のほかの issue
-
難易度 5/5 1週間以上 初心者へのやさしさ 25/100
-
難易度 5/5 1週間以上 初心者へのやさしさ 30/100
-
難易度 5/5 1週間以上 初心者へのやさしさ 20/100
-
UTF-8オープン
難易度 4/5 3〜5日 初心者へのやさしさ 25/100
-
難易度 3/5 1〜2日 初心者へのやさしさ 35/100
似ている issue
-
TLS: a stale OpenSSL error makes non-blocking reads fail with "Resource temporarily unavailable"オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1〜3時間 初心者へのやさしさ 82/100
-
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
bigtreetech/BIGTREETECH-TouchScreenFirmware#3056 ·
メンテナーはふだん 1 日以内に返信
-
Allow pillow 13オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
-
[pico][astrocade] emu/apply.sh edits src/mame/midway/astrohome.cpp, which current MAME has in bally/オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 83/100
FujiNetWIFI/fujinet-firmware#2120 ·
メンテナーはふだん 1 日以内に返信