caustic
caustic copied to clipboard
ashwin153
A transactional programming language.
One of the problems with using loops in Caustic is that reads within a loop must happen sequentially. If we can unroll the loop, then any reads in the loop...
Indexed fields of type ```F``` of a struct ```T``` are added and removed from an index of type ```Map[F, Reference[T]]``` on object creation and deletion. You could search and iterate...
A program may itself be composed of a number of independent programs; or programs that do not read or write any keys in common. These independent programs may be executed...
Add and remove structs of type ```T``` to a ```Map[String, T&]``` on creation and deletion. This would allow structs of a particular type to be searched and iterated. Related to...
Prefetching increases the conflict window. The earlier you ```get``` a key, the more likely it is that the key might be changed before the program finishes executing. In some applications,...
Submit a PR to [Rouge](https://github.com/jneen/rouge/wiki/Adding-a-new-lexer) to add a Caustic lexer. This will allow Caustic syntax highlighting from kramdown.
Formalize the tests that we have run on the standard library. ScalaTest has a ```compile``` macro that will be useful in verifying that the standard library is indeed type-safe.
- [Feature Request](https://www.reddit.com/r/programming/comments/7b338z/caustic_a_transactional_programming_language/dpfau9e/) - [Smart Cast](https://www.reddit.com/r/programming/comments/7b338z/caustic_a_transactional_programming_language/dpfe0lh/)
The key property of caustic is *safety* - what runs is what you wrote. One of the most fickle of all bugs is the truncation error caused by floating point...