Add less common languages to make this more useful

[TashaSkyUp]

I think the real possible value here is taking someone who knows programming in general or even programming very well but only in a few languages, and making them someone who can produce artifacts of any sort. For instance, yes I could take my time and create shader code. But the last time I did it was annoying.

So I guess some things on that list would be

C++ – High-performance libraries for Python bindings and WebAssembly for JavaScript.

Rust – WebAssembly modules for JavaScript and fast Python extensions.

Haskell – Compilers or parsers callable from JavaScript or Python.

Erlang – Distributed systems or APIs accessible via JavaScript or Python.

Prolog – Logic-based engines for AI in Python or JavaScript.

COBOL – Legacy data processing scripts integrated into modern APIs.

Ada – Safety-critical libraries exposed via Python or JavaScript interfaces.

Verilog/SystemVerilog – Hardware simulation results exportable to Python or JavaScript.

Kotlin Multiplatform – Cross-platform components callable from JavaScript or Python.

Assembly Language – Optimized binaries wrapped for Python or JavaScript usage.

You could also add syntax for of specifying runtime complexity and maybe a parameter for Max compilation time.

[kcaswick]

I just want to agree that I think it's very important to be able to specify runtime complexity or some other way to specify performance constraints, which is not covered by the example syntax.

One thing I noticed was every time I compiled, it randomly picked a different algorithm for satisfying the examples, which could change both performance and what edge cases need to be tested. Even if #4 is fixed, I think random performance would make it unusable for anything serious.