Erik Svedäng

Improve the Language Guide

13

- [ ] Needs an index at the top - [ ] A more gentle intro on how to call and define functions would be good, early on the page...

Currently you can only specify modules to generate docs for, so top-level bindings are left out (which is a shame, especially when they have nice documentation.) The whole situation is...

See `./test/test-for-errors/ref-as-member.carp`, the error becomes: ``` I can’t use the type `(Ref Int )` as a member type at no info. ```

Avoid printing lifetimes sometimes, and also print them in a nicer way

12

Right? Would make things a *lot* more readable...

Add `reductions` (scan) function for Array / StaticArray

1

see https://clojuredocs.org/clojure.core/reductions

A refactoring idea for errors

2

How about adding a typeclass that we implement for all the different error types in the compiler. It would have two methods, one for producing the long nice message (currently...

Ability to configure how arguments are passed to external compiler

4

Different compilers require different flags, order of arguments, etc. It would be super handy to be able to define this per compiler/platform, something like: ```clojure (defbackend windows-tcc {"compiler" "tcc" "lib"...

Profiling the compiler

4

So far very little work has gone into making the compiler fast. For the most parts I thinks it's "fast enough", but since there presumably are no big projects written...

Implement str/prn for array and deftype:s via `derive`?

8

Pros: - We can delete tons of gnarly code in the compiler - Can adapt to whether stringifying a type makes sense in your project (can avoid it in a...

Examples or docs

5

Hi, thanks for the library! I have searched for some example code using the library (or docs). Does anyone know of anything? Thanks, Erik