Describing Scala Puzzlers as "the collection" rather than a "central repository"
Merge pull request #54 from scalapuzzlers/change-description

Describing Scala Puzzlers as "the collection"
Corrected a bug in the explanation of puzzler #8. Thanks, Nermin!
Puzzler 27: Padded Answer
More devious multiple choice, expand answer a bit.
Merge pull request #56 from som-snytt/puzzle/padded-answer

Puzzler 27: Padded Answer
Added puzzler 27: "Keep On Padding". Thanks, @som-snytt!
Updated puzzler 27 ("Keep On Padding") based on a subsequent puzzler submission (https://github.com/scalapuzzlers/scalapuzzlers.github.com/pull/57) by Luc Bourlier
Formatting cleanup for puzzler 27
Aligned formatting of answers with e.g. puzzler 23
Removed empty newlines at the end of the puzzler template
Submitted a new version of puzzler 26 based on the original submission (https://github.com/scalapuzzlers/scalapuzzlers.github.com/pull/55) by Vassil Dichev
Corrected formatting of answers on puzzler 27
Reserving 26 for a Scalaz puzzler (see https://github.com/scalapuzzlers/scalapuzzlers.github.com/commit/970508082c8b81db1980117a7a4489c249d03ea4#commitcomment-2118399)
Updated attribution of 27 as requested (https://github.com/scalapuzzlers/scalapuzzlers.github.com/pull/56#issuecomment-10167725)
Updated #27 for more LOL, less loll.

This is not a definitive version, except for the title.

There are some style differences, like one-liners, reduced use of
braces, and an implicit class to enhance StringBuilder.

In a LOL vein, padTo is renamed pad2, and it is compared to the
padTo out of the box. (It must be renamed for the extension method.)

It seems to me that's worth addressing.  The tradition of puzzlers
is broadly educational.

Does this puzzler result in a pithy Effective Scala meme?  I feel
it ought to.  Maybe something functional like: "Be results-oriented."
Because not attending to a result type is the error.  I added the
suggestion to add type info to express expectation or intention,
to extract compiler help.

I don't think the Eclipse IDE has a mode yet where it shows all the
inferred types, the way it will show implicits.

The other thing that always comes up on the ML is, Can I already do
this with existing API.

Footnote, I originally assumed that r foreach sb.append(c) looked like
r foreach sb.append(c).apply, which is wrong. I could imagine adding
-Xprint:typer output so that people are aware that it's normal to
consult it.
Suggested changes and clean-ups, and expanded CBF discourse
Suggested comments and clarifications
Merge pull request #58 from scalapuzzlers/cast-away

Submitted a new version of puzzler 26 as puzzler 28
Added Puzzler 28 ("Cast Away"). Thanks, Vassil for the submission and Daniel Sobral and Paul Phillips for comments!