Closed michallepicki closed 3 years ago
I submitted https://github.com/AbstractMachinesLab/caramel/pull/63 and https://github.com/AbstractMachinesLab/caramel/pull/64 for the low-hanging fruits, I will update the issue description to reflect the state of main if/when the second one gets merged. edit: updated.
@ostera I am not sure what to do about the remaining ones, as they don't directly translate to Erlang operators or functions in the :erlang
module (I think, I may be wrong about some of them). Are any of these very common and expected to be working in OCaml code? Or should we remove them all from Core for now?
At this point feel free to trim down the stdlib whenever you find something that doeesn't immediately make sense. We'll have to time to harden and stabilize it before we get to 1.0.
Describe the bug When using many of the automatically included functions from the Core module, the Caramel code compiles, but Erlang code does not compile with
function x/N undefined
errors.To Reproduce
Create a file
main.ml
withRun command
caramel compile main.ml && escript main.erl
See errors:
Expected behavior When Caramel code compiles, Erlang code compiles. It's possible that not all of the above functions are necessary to be implemented for now, but I think it wouldn't be too hard to get them working?
Environment (please complete the following information):