Nathan Braswell 49c5e9da2f Added the lazy eval function thing.
Keeping it off is 5.3s
Turning it on is 6.8s
Forcing it on always, which I thought would cause compilation problems (and I guess just turns most optimization off, but does enough to remove vaus?): 2.8s
so using it the way I designed makes it worse
and using it to a degree I thought it would be buggy makes is way faster
Indeed, forcing it on all the time does cause it to error for larger cases, but it is interesting
So I'm not entirely sure where to go with that, I think smaller test cases and profiling number of calls or something is warrented
2022-01-10 01:26:56 -05:00
2021-08-01 00:23:41 -04:00
2020-09-06 22:10:59 -04:00
2017-02-02 00:46:36 -05:00
2020-05-12 16:22:41 -04:00
2020-05-12 16:22:41 -04:00
2020-05-12 16:22:41 -04:00
2018-05-22 20:14:15 -04:00
2020-03-10 12:57:28 -04:00
2018-04-17 11:25:53 -04:00
2020-04-02 14:15:41 -04:00
2021-08-01 00:23:41 -04:00

Kraken

The Kraken Programming Language

(try it out online at http://www.kraken-lang.org/)

(vim integration (filetype, syntax highlighting, Syntastic) at https://github.com/Limvot/kraken.vim) (emacs integration (filetype, syntax highlighting) at https://github.com/Limvot/kraken-mode)

The Kraken Programming Language is functional but very much still in development. It has both the normal features you might expect of a modern language, (functions, variables, an object system, dynamic memory), as well as some more advanced ones (mutually recursive definitions, lambdas/closures, algebraic data types, templates, marker traits, defer statements, etc).

Kraken can either compile to C or its own bytecode which is then interpreted.

Dependencies

Kraken is self-hosted - in order to build it, a script is included that will compile the original C++ version (which depends on CMake) and then checks out each necessary version to compile up to the current one. This can take quite a while - when it hits 1.0 I am planning on removing the old C++ version and checking in a pre-compiled-to-c version to use for further bootstrapping.

Goals

It has the following design goals:

  • Compiled
  • Clean
  • Fast (both running and writing)
  • Good for Systems (including Operating Systems) programming
  • Very powerful libraries (say, a library that allows you import from automatically parsed C header files)
  • Minimal "magic" code. (no runtime, other libraries automatically included)

It is inspired by C, Kotlin, Rust, and Jai.

Description
Currently, a purely functional F-Expr based Lisp compiled to WebAssembly. History contains multiple iterations of my experiments to explore and create my personal perfect language.
Readme 12 MiB
Languages
Rust 40.6%
NewLisp 12.7%
HTML 11.7%
Shell 7.5%
JavaScript 4.4%
Other 23.1%