employer
/
tame
1
0
Fork 0
Code Packages Releases Activity
tame/tamer/tests/xmli/expected.xml

22 lines
384 B
XML
Raw Normal View History

tamer: asg::graph::object::xir: Initial rate element reconstruction This extends the POC a bit by beginning to reconstruct rate blocks (note that NIR isn't producing sub-expressions yet). Importantly, this also adds the first system tests, now that we have an end-to-end system. This not only gives me confidence that the system is producing the expected output, but serves as a compromise: writing unit or integration tests for this program derivation would be a great deal of work, and wouldn't even catch the bugs I'm worried most about; the lowering operation can be written in such a way as to give me high confidence in its correctness without those more granular tests, or in conjunction with unit or integration tests for a smaller portion. DEV-13708
2023-02-22 23:03:42 -05:00
<package xmlns="http://www.lovullo.com/rater"
xmlns:c="http://www.lovullo.com/calc"
xmlns:t="http://www.lovullo.com/rater/apply-template">
<rate yields="rateFoo" />
tamer: Lower sum expressions This was a fairly simple addition, since rate blocks already lower into sum expressions; these are just non-identified. This does emphasize that the nir::parse `ele_parse!` abstraction I spent so much time on ended up not being a perfect fit, as it now has some boilerplate after it was stripped of much of its capabilities some time ago. Don't worry, `nir::air` and `asg::graph::xmli` will get cleaned up. DEV-13708
2023-02-22 23:45:23 -05:00
<rate yields="rateBar">
<c:sum />
</rate>
<rate yields="rateBaz">
<c:sum>
<c:sum />
</c:sum>
<c:sum>
<c:sum />
<c:sum />
</c:sum>
</rate>
tamer: asg::graph::object::xir: Initial rate element reconstruction This extends the POC a bit by beginning to reconstruct rate blocks (note that NIR isn't producing sub-expressions yet). Importantly, this also adds the first system tests, now that we have an end-to-end system. This not only gives me confidence that the system is producing the expected output, but serves as a compromise: writing unit or integration tests for this program derivation would be a great deal of work, and wouldn't even catch the bugs I'm worried most about; the lowering operation can be written in such a way as to give me high confidence in its correctness without those more granular tests, or in conjunction with unit or integration tests for a smaller portion. DEV-13708
2023-02-22 23:03:42 -05:00
</package>