# Using Playgrounds with this book

**URL:** <https://forums.kodeco.com/t/using-playgrounds-with-this-book/45510>\
**Category:** Data Structures & Algorithms in Swift\
**Created:** [August 5, 2018, 5:06am UTC](https://forums.kodeco.com/t/using-playgrounds-with-this-book/45510 "2018-08-05T05:06:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![thelonederanger](https://assets.chunter.kodeco.com/user_avatar/forums.kodeco.com/thelonederanger/32/81494_2.png) [@thelonederanger](https://forums.kodeco.com/u/thelonederanger)\
**Post date:** [August 5, 2018, 5:06am UTC](https://forums.kodeco.com/t/using-playgrounds-with-this-book/45510/1 "2018-08-05T05:06:35Z")

</div>

Hello fellow coders,

I am writing in the hope that someone here may have some solutions to a couple of issues I am having using playgrounds (not a book issue but the developer forums are failing me) while I am working through the code in this book.

I am finding playgrounds a very frustrating platform to work with. I have set “Run” to “Manually Run” which has seemed to solve the very slow times that playgrounds was taking to compile. While I am editing the files in the “Sources” folder I am continuously getting a popup alert that states “The auxiliary source module did not compile successfully”. Does anyone know a solution or workaround for this please. Any playgrounds streamlining solutions would be much appreciated.

Cheers

Jim

---

<div class="post-metadata">

**Author:** ![brianlawson](https://assets.chunter.kodeco.com/user_avatar/forums.kodeco.com/brianlawson/32/81494_2.png) [@brianlawson](https://forums.kodeco.com/u/brianlawson)\
**Post date:** [August 5, 2018, 2:44pm UTC](https://forums.kodeco.com/t/using-playgrounds-with-this-book/45510/2 "2018-08-05T14:44:25Z")

</div>

You’ve already found the known solution for problematic playground behavior – leaving them in Manually Run mode. I’ve also added a shortcut stolen from Xcode 10, using Command-Shift-Return to execute the playground.

You’ve probably already found that the “auxiliary source module…” message is caused by a syntax error in one of the source files you are not currently editing. I try to clear those up as soon as I become aware of them so they do not continue to get in my way as I’m working on new code.

---

<div class="post-metadata">

**Author:** ![kelvin\_lau](https://assets.chunter.kodeco.com/user_avatar/forums.kodeco.com/kelvin_lau/32/109371_2.png) [@kelvin\_lau](https://forums.kodeco.com/u/kelvin_lau)\
**Post date:** [August 8, 2018, 9:46pm UTC](https://forums.kodeco.com/t/using-playgrounds-with-this-book/45510/3 "2018-08-08T21:46:41Z")

</div>

I also feel your pain. I was hit with dozens of weird playground behaviour - some that hung forever.

Playgrounds has been a mixed bag from inception. Some releases were fairly stable, but the Xcode 9 ones have been problematic.

There’s been some promising changes for Xcode 10 playgrounds, so hopefully that will help make things easier to work with.