libera/#sicl - IRC Chatlog
Search
1:45:05
paulapatience
Ok, the default cleavir-environment:type-expand takes an entry env, and calls type-expand on (next env). I'm having trouble understanding how to map that to Trucler's way of doing things. From what I can gather, the old way (with cleavir-environment) was: every info is an entry, with a %next slot that points to the next info. And the new way (Trucler) is to have an environment which is augmented and keeps a list for each kind of description.
1:45:05
paulapatience
So should the new type-expand call itself on all the descriptions of a Trucler environment instance? (That doesn't seem to make sense, though.) I'm confused, probably because I don't fully understand environments yet.
2:15:54
Bike
paulapatience: if you go through cst-to-ast that should help with understanding environments
2:48:04
Bike
paulapatience: type information is all in the global environment, so any type-expand methods should be able to skip local information. that's what the next does. for trucler there's a global-environment function to get you straight to the global environment, i think.