tbc399 / cs378-deque Goto Github PK

Invite the graders to your private code repo.

Implement and debug the simplest possible solution in Deque.h with assertions that check pre-conditions, post-conditions, argument validity, and return-value validity, until all tests pass, and add, commit, and push to the private code repo.

push_front() is trying to do something with an invalid pointer when I go to allocate space for the new element up front.

There's some hideous flaw with the way I wrote pop_front() and pop_back() becasue they take way too long.

Create a dev branch in git

The copy assignment in my_deque is causing the valid method to trip in operator++()

Run Doxygen, which will create html/ [make html], that then documents the interfaces to your functions.
Create inline comments if you need to explain the why of a particular implementation.

Try and see where the iterator is relative to the ends of the deque. If it's closer to begin() then move the elements between begin() and the iterator. The same idea goes for when it's closer to end().

Create a log of your commits in Deque.log [make Deque.log].

Clone the public test repo onto your local directory [make deque-tests].

Clone your private code repo onto your local directory.

Copy your unit tests and to your clone of the public test repo, rename the files, do a git pull to synchronize your clone, and then add, commit and push to the public test repo.

Make at least 5 commits, one for each bug or feature.

Connect your Travis CI account to the dev branch of your private code repo.

Try and make it give out only the necessary space.

putting the iterator into an invalid state with the index being some junk value.

pop_back is failing on second unit test for pop_back.

Try and use move constructors to implement swap. I don't even know if that's possible, but I think the book said that's how swap should work.

Added the capacity method and need to add tests for it eventually.

Write unit tests in TestDeque.c++ that test corner cases and failure cases until you have an average of 3 tests for each function, confirm the expected failures, and add, commit, and push to the private code repo.