Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chapter 3: Why are the answers in the exercises files? #571

Open
SamKacer opened this issue Jun 8, 2019 · 1 comment
Open

Chapter 3: Why are the answers in the exercises files? #571

SamKacer opened this issue Jun 8, 2019 · 1 comment

Comments

@SamKacer
Copy link

SamKacer commented Jun 8, 2019

Started going through the book today and looking through the exercises for chapter 3, list.scala in particular, I noticed that the answers are left out for some exercises and for some they are pasted in instead of the unimplemented function signatures.

I expected the exercises files to be skeleton code for filling in with our answers and then if needed we could look up the answers in the answerkey directory. Why are they already in the exercise file? Doesn't that spoil the learning experience?

@otto-dev
Copy link

otto-dev commented Feb 20, 2020

I coincidentally opened this issue while I was reading the same chapter myself (I'm a student of the book as well).

I believe the exercise code looks exactly like it is supposed to look, as only the "examples" from the book have their implementation provided.

The book makes a distinction between examples and exercises. The examples, which are used for explanatory purposes in the book, are already provided. They have lost most of their value as exercises since the book reveals and talks about the code. Then the book follows up with exercises for the reader to implement - those are the functions with their implementation missing.

So examples: already implemented. Exercises: left to the reader.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants