Be sure to be prepared to discuss this problem set with the TA
in your lab. Here are some general notes to pay attention to
for this problem set and all future problem sets:
Style: This has been said a few times but we repeat, before
submitting run your file (ctrl/cmd + r). You should also indent
your file regularly using (ctrl/cmd + i).
You should erase the three bangs (!!!) after you have
fulfilled a wishlist entry.
Purpose statements are a required step of the recipe and they
should be kept strictly under 80 characters and on one line.
Stubs are a required step of the recipe and to be sure that
your tests and your stub are correct you should run your tests
with your stub. Remember that the result type of your stub
should match that of your signature. Just because these have
fulfilled their purpose by the time you hand in doesn't mean
that they weren't important or that we aren't checking
them—TA problem set assessment is a significant part of
your problem set grade.
You must follow the complete HtDF recipe for every every
function you design, even if it is a helper. This includes tests,
which should be both valid and thorough.