A few Swift developers move in to its own,
should read:
A few Swift developers move in to its own line,--Gary Scarr

Reported in:
P1.0
(20-Apr-17)

#81454Paper page: 75

Under "Chaining Calls", `myInstance.surname.characters.count` is referred to as a fluent interface. The implication seems to be that any call chain is a fluent interface. But the Wikipedia page in the footnote says that a fluent interface entails more than just method chaining. Martin Fowler's bliki page on the term says that typically fluent interfaces are used for configuring objects, and that the key is that they're providing a domain-specific language. It seems to be primarily for setters, not for getters. So it doesn't seem to me that just drilling into properties of objects qualifies as a fluent interface. At the very least, it's debatable whether that term applies, so it may be best to qualify it.--Josh Justice

Under "Chaining Calls", `myInstance.surname.characters.count` is referred to as a fluent interface. The implication seems to be that any call chain is...more...

"prefer mentioning every case than catching final cases with default". This seems to take the construction "prefer X than Y", but I think typically you'd say "prefer X to Y." So "prefer mentioning every case TO catching final cases with default"--Josh Justice

"prefer mentioning every case than catching final cases with default". This seems to take the construction "prefer X than Y", but I think typically yo...more...

Reported in:
B4.0
(19-Mar-17)

#81209PDF page: 126

In last paragraph, I believe that "more flexibility" should be changed to "more flexibly".--Sean