I need to finish something presentable by May so I decided to make Orchid an untyped language, and the simplicity of all tasks all of a sudden breaks my heart. Static analysis is my guiding principle, the one feature which I always held to be good. Deprioritizing it in _my own programming language_ feels like sacrilege.

Is this an MVP you’re working on?

@red-knot As it currently stands, the MVP won't even accurately represent the planned full product, but yes.

You are entering the wild west then there my friend. But I can understand it. Deprioritizing static code analysis might let you finish the project sooner albeit you will end up with something that you do not want. At the time and from your previous posts it seems that you are doing this for school, is this assertion correct?

@AleCx04 That's right.

Types are bolted on later these days. Typescript, TypedLua/Teal, C++ (C With Classes). 😉

@MegaLeetBro The annoying part is exactly that originally Orchid was going to match typeclass implementations to generic arguments through type unification, so anything I come up with in that area for this reduced version of the language will be a tangential step to the direction where I'd like to get eventually. I'm inclined to just not offer dynamic dispatch at all for the time being and recommend a monomorphic programming style a little bit like how React uses javascript.

At least I'll have lexical scoping and haskell-style lazy datastructures, I think most programmers can figure out how to use these efficiently even without classes.

s/dynamic dispatch/typeclasses/

@MegaLeetBro

A) C++ is not "C with classes".
B) what in the world makes you think C++ is an example of types being bolted on later?