freenode/#sicl - IRC Chatlog
Search
8:32:55
heisig
And a final remark - I'd like to add a predicate NULL-LEXICAL-ENVIRONMENT-P to Trucler. Does that sound reasonable?
9:48:36
beach
So for HIR-to-MIR, I want to process each function at a time, except that I don't want to process the top-level function at all. After closure conversion, the functions in a compilation unit are almost entirely independent. The only dependency is that the ENCLOSE-INSTRUCTION refers to some ENTER-INSTRUCTION. The ENCLOSE-INSTRUCTION will be translated to a call to allocate a function object, and the reference to the ENTER-INSTRUCTION
9:48:37
beach
will ultimately be replaced by an entry point, which is an index into a byte vector that contains native instructions.
9:51:39
beach
I should probably also import the idea from Cleavir1 where the ENCLOSE-INSTRUCTION is separate from the instruction that sets the static environment.
10:01:34
beach
Aside from those considerations, I think HIR-to-MIR is sufficiently complete as it is.
12:59:46
heisig
I just created a Github organization 'sicl-developers', where we could collect all SICL related repositories (as scymtym suggested).
13:00:46
heisig
beach: You should have received an invitation to become one of the owners of this organization.
13:02:39
heisig
Owner is a slight misnomer, because the real owner of all Github projects is Microsoft...
13:04:52
heisig
Unfortunately, the name 'SICL' was already taken. But I have contacted that person, maybe he is willing to change his account name.
13:14:44
heisig
I am also tempted to change the description of the organization to 'X Implementors of Common Lisp', for X being some sensible adjective starting with S.
13:23:43
beach
heisig: I also have no preference, but I know scymtym is thinking in much more general terms than SICL.
13:24:32
heisig
Right. Maybe we should wait for feedback from scymtym before we make any next steps.
13:30:23
beach
Like, scymtym is working on things like a module that defines many characteristics of every Common Lisp special form, including syntax, indentation, etc.
14:28:23
scymtym
i was going to say that, but then i realized that there would be a cost to renaming. initially a small one but increasing with actual use of the organization
14:30:16
scymtym
i had my share of name finding discussion and it was a nightmare every time. so i'm not sure how to proceed
14:32:04
scymtym
yeah, choosing names when multiple people are involved is the worst (despite everyone's best efforts)
14:50:37
scymtym
beach: i like it since some of the modules are providing machinery that is usually reserved for implementors to users as well as implementors
15:00:34
heisig
Hmm, 'reclaiming' sounds too militant for my taste, like we'd be fighting other tribes of programmers.
15:02:20
scymtym
knowing beach, it is probably 1/3 straightforward, 1/3 joke and 1/3 to annoy people who get annoyed by such things :)
15:19:57
beach
A milder possibility would be to reuse the title of a book I imagined I would write: Common Lisp for Language Implementers.