(When you are done, please submit your solution using the Fire system)

In this lab assignment, you will get experience of parallel mostly-functional programming in Java 8. The exercises are associated with Peter Sestoft’s lecture on April 28 2016.

Note: Please make sure you follow the submission guidelines when you write your code.

Submit the answers to all the exercises provided by Peter: Exercises in Parallel Functional Programming in Java

Getting more practice

If you have run out of assignments, consider tackling k-means from Marlow’s book. You should be able to parallelise both the Assignment and Update steps using Java streams. We can persuade Peter Sestoft to provide a skeleton sequential implementation if there is demand for this. This part of the lab is not obligatory.

Submission

This lab has two deadlines:

• First deadline (Thursday, May 5 at 23:59): You need to have made a serious effort on all obligatory parts of the lab assignment.
• Final deadline (Thursday, May 12 at 23:59): You need to have passed the lab unless you have requested and been given an extension.

Your submission needs to include the following information:

• The Java code containing your solutions. Call it LabCxx where xx is your group number (or something similar if you have several files).

• report.txt or report.pdf, a file containing brief documentation of what you have done (e.g. time measurements asked for) and the answers to questions posed on the exercise sheet. Submit the files separately (no tar or similar).

Before you submit your code, Clean It Up! Remember, submitting clean code is Really Important, and simply the polite thing to do. After you feel you are done, spend some time on cleaning your code; make it simpler, remove unneccessary things, etc. We will reject your solution if it is not clean. Clean code:

• Does not have long lines (< 78 characters)
• Has a consistent layout (do not use TAB characters in your code)
• Has type signatures for all top-level functions
• Has good comments
• Has no junk (junk is unused code, commented code, unneccessary comments)
• Has no overly complicated function definitions
• Does not contain any repetitive code (copy-and-paste programming)

When you are done, please submit using the Fire system.

Good luck!