freenode/#clasp - IRC Chatlog
Search
14:29:32
Bike
::notify karlosz i think create-cell in the fucntion body should be okay. fetch wouldn't be, but i don't think you changed that.
14:38:57
beach
Bike: Are you working on getting the compilation of LET used in Generate-AST to work for CST-to-AST?
14:42:52
drmeister
We ran into a problem with the PR - it fails compiling something in our code base - Bike has the details.
14:44:34
drmeister
I'd like to take a hard look at it now and see what is going on and whether the problems are simple bugs or more serious - I'd like to go forward with it if it is a correct update to the compiler.
14:45:38
drmeister
I think I have my problems squared away with jupyterlab and controlling python and javascript package versioning. (oh please oh please oh please)
15:19:42
beach
Bike: By the way, have you given any more thought to counting the number of times each instruction gets inlined?
15:20:07
Bike
no, i've been focusing on something else, but it's not going anywhere so i can do that tomorrow
15:21:07
Bike
trying to clean up clasp's lambda list argument parsing, and fix how it works for generic functions
15:24:14
beach
heisig: Any my wife (and most Americans) stick a comma before the AND in an enumeration: "fast, precise, and portable..."
15:28:25
beach
Chapter 2. The name "monitoring region" make the reader think about some region of code. Then it comes as a bit of a surprise that it's a class.
15:30:08
heisig
The idea was that users might want to have different profiling regions, e.g., for performance-critical code, for recursive code etc. But I am not sure whether this is worth the added complexity.
15:30:58
beach
You mention "where the active region is bound to..." suggesting that there is some active region at any point in time, but this is not elaborated upon I think.
15:33:38
heisig
I see the description definitely needs some examples. About the name, I am not so sure myself. Probably a symbol.
15:35:31
beach
In inter/leave-monitoring-region, what is the nature of the parameters? Names or instances of the corresponding classes?
15:36:07
heisig
drmeister: No, I didn't. Has my behavior changed so drastically or why do you assume so?
15:37:13
heisig
Ok, back to the regions. In an act of premature optimization, I had the idea to have monitoring regions created at load time.
15:37:59
beach
I say, make a second pass on the document and remove what you don't think is necessary. And try to explain the rest to slow thinkers like myself.
15:38:37
heisig
I also need to dig into some other profiling libraries I found, most notably, easy_profiler (https://github.com/yse/easy_profiler)
15:39:13
beach
drmeister: We got married for legal reasons. We didn't want our respective families to inherit half of the house. We could have made a testament, but then there would be huge taxes on the inheritance.
15:40:30
beach
drmeister: Interestingly, a woman who gets married in France keeps her last name for all legal purposes.
15:40:57
heisig
In other news - I also got my new computer with more RAM and I managed to compile clasp without issues. Now I can try to incorporate my load-time-value-stuff.
16:45:23
drmeister
My wife's maiden name is "Worms" - I suggested that she could keep it - but she decided to take my family name.
16:51:34
drmeister
I build cando on an AWS machine running Debian 10 and I run cando once to get quicklisp to compile all of the cando quicklisp packages. Then I create a tarball of the /opt/clasp directory that contains everything including the quicklisp cache. When I run the docker image it insists on recompiling all of the quicklisp again - grrrr
17:07:52
drmeister
I'm pretty sure it's derived from "Vermes - all non-arthropod invertebrate animals" - and no one is going to convince me otherwise.
17:15:18
beach
I guess it must be *possible* to change your name here in France. I remember a student (woman) whose name was Couillard and she was very happy to take the husbands name.
17:16:28
drmeister
ACTION has been wrangling with Python and Javascript and not learning French. "Couillard"?
17:27:09
drmeister
The ~/.cache/common-lisp/xxxx/... tree contains absolute pathnames - and the contortions that I'm taking to build things on the AWS machine are not taking that into account properly.
18:14:01
Shinmera
I had a hacky patch that fixed it, but it did it in a way that wasn't entirely right and broke with some libraries so I had to remove it again
18:15:09
drmeister
I'm building everything relative to /opt/clasp - I tried to get clever and build it in a local directory and symlink /opt/clasp to it - but asdf was having none of it.
18:17:51
Shinmera
Here's an email chain that I sent to ASDF devel once https://mailman.common-lisp.net/pipermail/asdf-devel/2017-December/005993.html
18:28:12
drmeister
My solution is easier than yours - I'm going to build at /opt/clasp and install at /opt/clasp
18:28:34
drmeister
I was trying to be fancy and build at wherever/opt/clasp and then install at /opt/clasp
18:31:59
drmeister
Bike: We still have the source-debug-pathname option for compile-file. IIUC Fare was suggesting in the email chain that an option to compile-file that substituted an arbitrary logical pathname for source info would be a good solution to Shinmera's problem.
18:32:40
Bike
i think the function descriptions have a T_sp for the pathname, so i guess that's fine
18:33:21
drmeister
I don't think so - but it might be a good idea to implement Fare's idea as a generalization. I'm a bit confused as to what source-debug-pathname does these days - do you recall?
18:36:30
drmeister
Right - so a better names for the source-debug-xxx arguments might be source-tracking-pathname and source-tracking-offset and then allow source-tracking-pathname to use logical pathnames?
18:37:34
drmeister
The idea is that the output of a C-c C-c compile-file operation is a small fasl that with source tracking info that points to the original file and offset in the original file - correct?
18:39:54
drmeister
If it permitted logical pathnames then we have the clasp implementation details for what Fare is proposing here https://mailman.common-lisp.net/pipermail/asdf-devel/2017-December/005996.html (less the changes to ASDF).