one obvious omission is algebraic datatypes. i wonder if this turns out to also apply to languages that want the sort of golang interop that oden aims for.
edit: apparently there’s a plan for runtime-dispatched sum types
[Comment removed by author]
If you’re already generating code, you can just generate a copy of the generic with the specific type signature.
Wait, what? Oden originally started out as a sexp based Lisp! When did they change directions? (Not that this is necessarily a bad thing, mind you)
Oskar has actually written a blog post on the reasons for moving from Racket to Haskell, which you can find here: http://oden-lang.org/blog/compiler/2016/01/18/the-haskell-rewrite.html
When life hands you lemons…
one obvious omission is algebraic datatypes. i wonder if this turns out to also apply to languages that want the sort of golang interop that oden aims for.
edit: apparently there’s a plan for runtime-dispatched sum types
[Comment removed by author]
If you’re already generating code, you can just generate a copy of the generic with the specific type signature.
[Comment removed by author]
Wait, what? Oden originally started out as a sexp based Lisp! When did they change directions? (Not that this is necessarily a bad thing, mind you)
Oskar has actually written a blog post on the reasons for moving from Racket to Haskell, which you can find here: http://oden-lang.org/blog/compiler/2016/01/18/the-haskell-rewrite.html
When life hands you lemons…