Opened 6 years ago

Last modified 4 years ago

#197 new task

Think through and clean up various TempBlock classes

Reported by: dagss Owned by: somebody
Priority: major Milestone: wishlist
Component: Code Generation Keywords: cleanup

Description currently have two different TempBlock?-style classes. These fit different purposes, but are still too dissimilar etc. One unifying concept like a LetNode (or two different ones, one statement and one expression, but still a similar API) should be introduced before it is used in too many situations.

This work should ideally include getting rid of the ugly hack I'm about to commit in TreeFragment, where a full variable is allocated rather than a temporary. See #151 for details.

Change History (3)

comment:1 Changed 6 years ago by dagss

TempNode? should go into this as well. It doesn't work well as it is because with a single ExprNode? temp acquisition and node evaluation is intimately linked, and this doesn't fit where TempNode? has been used.

comment:2 Changed 5 years ago by robertwb

  • Milestone changed from 0.12 to 0.13

comment:3 Changed 4 years ago by robertwb

  • Milestone changed from 0.13 to wishlist
Note: See TracTickets for help on using tickets.