freenode/#clasp - IRC Chatlog
Search
3:40:43
Bike
what's supposed to happen is, if the constant is already defined, it just redefines it to itself, which is no problem
12:48:22
Bike
beach: about storing docstrings in cleavir - in clasp we have enter instructions that store function names, and then the translate-to-llvm step specially load time value hoists it. i'm not sure how else to deal with it, since it's more a property of the enter than of the enclose even if enclose is what does the allocation- and if it's not a normal input to something it won't be hoisted normally.
12:51:49
attila_lendvai
drmeister: I stopped working on the build refactor for now. I'd fancy some quick feedback on it if you see anything objectionable: https://github.com/drmeister/clasp/pull/419
13:33:49
drmeister
frgo: Everyone here is excited about pybind11 - a lighter weight binding library between C++ and Python. https://github.com/pybind/pybind11
13:34:21
drmeister
It looks like boost.python where they stripped away a lot of boost dependencies and took advantage of C++11's variadic templates.
14:20:52
Bike
can't really reconstruct a lambda list suitable for debug from the enter-instruction's
14:30:48
Bike
drmeister: why does init.lsp make a bunch of compiler variables special? stuff like *clang-bin* that isn't used until bclasp
14:58:11
beach
Bike: Sorry, was busy making lunch for my favorite coauthor and then working in the afternoon.
14:59:04
beach
I haven't really thought much about docstrings. Is there anything you want me to give some thought? Or perhaps you have some direct question?
15:00:36
Bike
Well basically I want cleavir to be able to compile functions with docstrings. It can't right now, it discards them.
15:04:32
Bike
I think it makes sense to store it in the enter instruction. Then when an enclose is being translated it can grab that docstring and do whatever it does.
15:12:30
beach
True that. And this problem is implementation specific. We need an implementation-specific way of compiling ASTs in LOAD-TIME-VALUEs.