You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Title pretty much.
Placeholder for a solution :D
Why do you think mal, despite being written in all sorts of, inclufing obscure, languages still doesn't have a coq implementation?
There may be some issue in running mal in pure coq, as it was not really intended[citacion needed], and may be even counter productive as it doesn't have a "usable-ish enough" IO functionality.
Coq programs however can be exported into other languages, for example: Ocaml, R5RS, and adapted using those. The benefit of using coq for mal may be:
design, spec verification;
set basis of verified implementation stepping up it's implementation standard;
may improve program and library reusability;
Mal can become somewhat more or less production ready? 😅
Even if it isn't really a project goal, I'm curious to hear your opinion.
The text was updated successfully, but these errors were encountered:
I'm working on cleaning up issues to be a bit more manageable for me so I'm going to close this for now. That doesn't mean I don't want a Coq implementation. I would love to see it when somebody is able to submit a PR for it.
Title pretty much.
Placeholder for a solution :D
Why do you think mal, despite being written in all sorts of, inclufing obscure, languages still doesn't have a coq implementation?
There may be some issue in running mal in pure coq, as it was not really intended[citacion needed], and may be even counter productive as it doesn't have a "usable-ish enough" IO functionality.
Coq programs however can be exported into other languages, for example: Ocaml, R5RS, and adapted using those. The benefit of using coq for mal may be:
Even if it isn't really a project goal, I'm curious to hear your opinion.
The text was updated successfully, but these errors were encountered: