Closed gelisam closed 1 year ago
@sorawee, would you like to try reviewing this PR? I can walk you through the Klister syntax if you want, either via PR comments or a video call.
@gelisam thanks very much for the invitation! Unfortunately, I won't be free until this Saturday. I will definitely take a look at this later. But please proceed without my inputs.
Unfortunately, I won't be free until this Saturday.
Take your time!
@sorawee , do you still plan to review this PR? No rush, just making sure you didn't forget :)
Oops, sorry!
Let me take a look at this tomorrow (this time for real, but if I don't again, definitely go forward without me!)
I see that added files are under the examples
directory. Would it be better to rename it to prelude
or lib
that conveys that these files are not just demo/tests, but something that is encouraged to be used?
Obviously, if you think it makes more sense to do that in a separate PR, that works too!
EDITED: I just saw that there are actual examples/tests at the end of the file. Those bits seem to be appropriate in the examples
directory. I still think the actual macro should be moved somewhere else.
I see that added files are under the
examples
directory. Would it be better to rename it toprelude
orlib
that conveys that these files are not just demo/tests, but something that is encouraged to be used?
For now, almost everything goes in ./examples
. #54 tracks the task of organizing which modules go in #lang "prelude.kl"
, which modules go in ./stdlib
, and which modules should stay in ./examples
.
I was waiting for @sorawee to do a second review after I addressed their comments, but I think I already took enough of their time. Merging!
Oops, sorry! I didn't you were waiting for a second review. Please merge it. It looks good to me.
Implement a
defuns
macro which allows the definition of mutually-recursive functions.Fixes #160.