star VS skybison

my own language Star! enjoyability is one of my main goals with the language, along with the "powerful, productive, and predictable" line

This is actually done by several bootstrapped languages, such as Crystal, Nim, Raku, and even my own language Star

In Star, commas and newlines are analogous everywhere, even inside array literals. This actually solves the issue of trailing commas by not needing commas at all

I really like Nemerle's OOP+FP hybrid model, and I've taken a lot of it to heart while designing my language Star, which is similar in spirit.

Most languages are afraid to for some reason, most likely because it "breaks tradition" or whatever. The only languages I'm aware of that allow this are Hack (for C-like enums) and my language Star (for both C-like and OCaml-like enums)

It's currently a work-in-progress, mainly due to subtyping issues with generics (which I'm honestly too lazy to fix rn, focusing on other stuff first). the code is located here, although be aware that it's a bit messy lol

Making lots of progress on Star's typechecker, which has been very difficult due to its expansive type system. Although still not completely finished or useable, it does at least work a bit. Currently need to implement type variable expansion/substitution, "lazy" type refinement (because I have no clue what else to call it), and some basic support for existentials

I think this is referred to as partial or lazy initialization. I have this feature in my own language Star (which us null-safe), but I don't have an actual null literal for this purpose

Sure I guess, here's one for Star: ``` You appear to be advocating a new: [X] functional [X] imperative [X] object-oriented [ ] procedural [ ] stack-based [X] "multi-paradigm" [ ] lazy [ ] eager [X] statically-typed [ ] dynamically-typed [ ] pure [X] impure [ ] non-hygienic [ ] visual [X] beginner-friendly [ ] non-programmer-friendly [ ] completely incomprehensible programming language. Your language will not work. Here is why it will not work.

Hello, I'm the developer of the Star programming language, and I have some questions about how to typecheck several new/uncommon features that it has, and looking for feedback on it in general.

The parent comment is referring to the primary Python interpreter and runtime, CPython, not to libraries. There are of course other Python implementations, but [the only C++ one](https://github.com/tekknolagi/skybison appears to be unsupported.

Kind of! In my fork I run microbenchmarks on each PR. So you can see on, for example, https://github.com/tekknolagi/skybison/pull/456, that the change had a 3.6% improvement on the compilation benchmark. If you expand further, you can see a comparison with CPython 3.8. Unfortunately Skybison is still on 3.8.

This is also the pointer tagging scheme from the Ghuloum paper. I did not design it. Another tagging scheme I did not design is the Skybison scheme, which uses 0bXXX...XX0 to tag integers and 0bXXX...001 to tag heap pointers. This makes heap reads very easy (bias by -1 in addressing mode).

Skybison is a Python interpreter and I'm curious what the results look like. We also have some benchmarks in benchmarks/benchmarks.

If you take a look at the Skybison Python runtime, I would be happy to chat and help you poke around integrating it: https://github.com/tekknolagi/skybison

I am, in fits and starts, writing a bytecode optimizer for Skybison that takes advantage of type information.