Commit a4e91fd1 authored by Danny Allen's avatar Danny Allen
Browse files

Updates write-up for 18au

parent d6cb956c
Pipeline #140825 failed with stage
in 0 seconds
......@@ -36,12 +36,8 @@ TODO: Answer this question
-----
## WorkLists ##
### peek(i) ###
The ADT for a WorkList explicitly forbids access to the middle elements. However, the FixedSizeFIFOWorkList has a peek(i) method which allows you to do exactly that. Why is this an acceptable addition to the WorkList ADT in this particular case? Why don't we do this in general?
In other words, what about fixed-sized FIFO worklists makes peek(i) make sense? Why does peek(i) NOT make sense in other worklist implementations?
**You should consider only the interface**, NOT the underlying implementation of our FixedSizeFIFOWorkList.
### WorkList Interface ###
We've implemented several data structures that all share the WorkList interface. What is the advantage of having several data structures with the same interface? Why not give each of them their own interface?
<blockquote>
TODO: Answer this question
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment