elucent / basil

Stack-based, multi-paradigm language with an emphasis on metaprogramming.

hey i'm david, usually "elucent" on the internet

• i'm currently working on basil, a programming language of uncertain direction
• i like to make lightweight, low-level libraries
• i used to make minecraft mods in high school
• i have a website with a tacky webgl cube on it. bonus points if it actually works on your browser

---

you can reach me:

• on twitter
• on discord

---

{⊃1 ⍵ ∨.∧ 3 4 = +/ +⌿ ¯1 0 1 ∘.⊖ ¯1 0 1 ⌽¨ ⊂⍵}

basil's Issues

Future plans?

Wow, this is actually kind of an impressive language. Disclaimer: I'm a bit crazy into languages.

I read the TODO documenting mainly the development 3 months ago. It feels Basil has lots of potential! What actually convinced me was the post about stack allocation with copying instead of any heap allocation (that's an older idea some concatenative languages and Fortran etc. use to get up to speed). As a side effect this could make Basil one of the very few fastest languages for Wasm.

I wonder whether there are any plans for Basil? IMHO Basil would deserve some real use cases and for that the first thing needed is seamless first-class support for something like FFI.

I'd be also very much interested if you could comment on the points outlined in arturo-lang/arturo#23 (comment) and then the points in henrystanley/Quark#2 .

Basil seems to have the hardest part kind of solved - namely the decision "eval everything in compile time and make an AST subtree as fallback" (the splice principle) which is something I'm crazy about (see e.g. sassert and assert and claim from the linked issues above).

Thoughts? Comments? I'm really excited about Basil so far!