freenode/#sicl - IRC Chatlog
Search
10:04:50
Shinmera
Probably one of the weirdest commit messages I've had to write https://github.com/robert-strandh/Stealth-mixin/pull/1
10:09:16
beach
no-defun-allowed: As a matter of fact, the paper on stealth mixins was accepted at a conference in Melbourne and I was there to present it.
10:14:10
beach
I was living in Auckland when we submitted the paper, but I was back in France when the conference took place, so I had to go halfway around the world just to present the paper. My coauthor, Johh Hamer, lived in Auckland, but refused to go.
11:12:22
beach
If I call the blue function compute-discriminating-function, then the red compute-discriminating-function will compute its discriminating function.
11:13:02
beach
After that, the blue compute-discriminating-function can be used on any yellow object, or rather, any object that has a blue class.
11:13:41
beach
So if I modify the blue generic functions to have blue classes, then the blue compute-discriminating-function should be able to compute the discriminating function of any blue generic function.
11:28:54
splittist
beach: it might help in explaining if you invented a mini-version/example of the acyclical->cyclical transformation your technique is pursuing. The best thing is - you could call it Caligula (:
12:09:10
scymtym
beach: as we discussed, there is sometimes, say when doing static analysis, a need for a "model" of the package system (including symbols). i already needed such a thing several times so i think it should be a reusable component. one thought was adding it to eclector, but that seems like scope creep. what do you think
12:14:36
beach
But sometimes a module I write is initially part of something existing, and I extract it later. Eclector is an example of that.
12:15:40
scymtym
of course. i'm only considering the possibility because i already have written and used it in several places
12:19:24
scymtym
i feel like this path leads to a strange situation. is a "model" of the package system the same as an implementation of the package system? should such a library try to be usable in common implementations? the situation was less confusing for eclector