From 433f0a44965ebbfe0d7eb23598ad6ab11c5c04a2 Mon Sep 17 00:00:00 2001 From: Patricia Aas Date: Thu, 7 Oct 2021 12:45:14 +0200 Subject: [PATCH] Remove unique_ptr exercise --- exercises/17/README.md | 2 -- exercises/17/unique_ptr_pacman/README.md | 17 ----------------- 2 files changed, 19 deletions(-) delete mode 100644 exercises/17/unique_ptr_pacman/README.md diff --git a/exercises/17/README.md b/exercises/17/README.md index 5041638..40bdec3 100644 --- a/exercises/17/README.md +++ b/exercises/17/README.md @@ -1,3 +1 @@ [< Back](../README.md) - -* [Exercise: std::unique_ptr](unique_ptr_pacman/README.md) diff --git a/exercises/17/unique_ptr_pacman/README.md b/exercises/17/unique_ptr_pacman/README.md deleted file mode 100644 index b8b6fa3..0000000 --- a/exercises/17/unique_ptr_pacman/README.md +++ /dev/null @@ -1,17 +0,0 @@ -[< Back](../README.md) - -# Exercise: std::unique_ptr - -## Background: - -(corentin: maybe something about } that destroys things) -We are going to play with using std::unique_ptr as we discussed in the slides. Since we will be reverting these changes -back, do take a copy of the GameState files before we start. We will change PacMan within GameState into a std:: -unique_ptr, once this has been done the code will not compile, because there are further changes needed within -the GameState class. Go through and figure out what needs to be updated. Can we change one of the ghosts into a std:: -unique_ptr? Are there any current design problems we will run into? What do these design issues say about ownership of -data? - -## Exercise - -1.