Create a record and pass that around in the rewrite rules. #41
Conversation
basic necessary infrastructure for performing conditional rewrites.
|
I'm not sure what you have in mind. Somewhere someone has to know about the targets, and this is a nice first order representation. I guess you could define each target as a list of rewrite rules and conditionally apply them, but that makes it harder to debug since you're passing opaque functions around. I'm not particularly attached to the current solution so if you want to change it go ahead. It's just one implementation of making a record and passing it around to the rewrite rules like Emil suggested in some other ticket. It might also be possible to change the contents of the record without changing much else if that was what you had in mind. |
|
Lets go with your solution for now. |
Create a record and pass that around in the rewrite rules.
|
I agree that we shouldn't let details of the back ends leak into the language package. It should be possible to add a back end (including conditional rewrites) without recompiling the language package. I've created issue #45 to fix this. (Anyway, this is a good step forward!) |
This is the basic necessary infrastructure for performing conditional rewrites.