Skip to content

typo: Missing parens in code example #20

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.

Sign up for GitHub

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

Open
olleolleolle wants to merge 1 commit into
base: master
Choose a base branch
from
Open

typo: Missing parens in code example #20

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions manuscript/markdown/mainmatter/1.objects/4.composition-and-extension.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ Consider a [queue]:
pullHead: function () {
var value;

if tail >= head {
if (tail >= head) {
value = array[head];
array[head] = void 0;
head += 1;
Expand Down Expand Up @@ -171,4 +171,4 @@ Now we can extend a queue into a deque:

Presto, we have reuse through extension, at the cost of encapsulation.

T> Encapsulation and Extension exist in a natural state of tension. A program with elaborate encapsulation resists breakage but can also be difficult to refactor in other ways. Be mindful of when it's best to Compose and when it's best to Extend.
T> Encapsulation and Extension exist in a natural state of tension. A program with elaborate encapsulation resists breakage but can also be difficult to refactor in other ways. Be mindful of when it's best to Compose and when it's best to Extend.