14:24:22beachBike: If we wrap every reference to a lexical variable in a THE, even if the type is T, we would not need a new type of AST to store the source information for the reference.
14:24:41beachWhat do you think of that suggestion?
14:26:05beachSo we can't have different source information for different occurrences.
14:26:46beachNo, a new AST type would not be expensive, but phase 2 has to be modified to deal with it.
14:27:19Bikeputting source information in THE seems weird, since you can use it for more complex forms that presumably have their own source information, and also we might want the THE to track its own source information (eg if it's from a declaration)
14:57:25frgoI checked visually from aboard MS Spitsbergen ;-)
14:57:58beachIs this work, or are you on vacation?
14:58:48frgovacation - a trip I was planning on doing for years. And yeah, it's worth doing ...
14:59:10beachSo I hear. I'm not going to try though.
15:01:46frgoI am just reading the logs of this channel here. I see you have been working on cst-to-ast stuff. Hmpf - I really need to read up on this...
15:03:58frgowell, sitting here in bright sunshine, sipping on a cup of cappuccino, while doing some hacking and reading fun stuff - that's vacation at it's best.
15:45:17frgo::notify epipping The comment you made on that signal waiting loop: It is intended to stay in the loop there. As I am the author of that particular piece of code I re-checked and can confirm: Works as intended.
15:45:17Colleenfrgo: Got it. I'll let epipping know as soon as possible.
16:25:01Bikei can't just drop in Integer_O::create because the function isn't declared
22:17:48Bicyclidinefrgo: trying to load quicklisp now... but yeah, sometimes changes to the inline definitions need some dist cleaning (or just erasing fasls specifically)