Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 90ba9a2

Browse files
author
Kristen Borg
committed
final edits
1 parent c3f2f5a commit 90ba9a2

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

02_composite-data/2-22_multiple-values/2-22_multiple-values.asciidoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -124,7 +124,7 @@ reimplement any of the core map methods (+assoc+, +dissoc+, etc.). It is only th
124124
semantics of the new behavior that differ from those of regular maps. Clojure defines very strong semantics around core
125125
functions. Breaking or overriding these expectations is always a bad
126126
idea, especially when using a distinct set of functions makes it clear
127-
when multimap functionality is being used.((("Clojure", "clojure.lang.Associative")))
127+
when multimap functionality is being used.((("Clojure", "clojure.lang.Associative", id="ix_cloj-lang-assoc", range="startofrange")))
128128

129129
The concrete implementation of +MultiAssociative+ extends the protocol
130130
to the +clojure.lang.Associative+ interface. It would certainly be
@@ -166,7 +166,7 @@ can be read with +get-all+, and values inserted using +insert+ can be
166166
removed with +dissoc+. All expectations regarding normal maps should
167167
hold. In the case of a normal +get+ on a key with multiple values, a
168168
set containing multiple items will be returned. This is probably what
169-
the user would expect upon inspecting the data.((("Clojure", "clojure.lang.Associative")))
169+
the user would expect upon inspecting the data.(((range="endofrange", startref="ix_cloj-lang-assoc")))
170170

171171
There is one more feature of this code that deserves commentary: the
172172
use of +::multi-value+ metadata on the sets used to store multiple

04_local-io/4-19_handle-binary-files.asciidoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -120,7 +120,7 @@ prepare it for reading and writing, respectively.
120120
==== See Also
121121

122122
- For more details on +ByteBuffer+, which plays a key role in Java's NIO
123-
library, see the http:/bit.ly/javadoc-nio[Java NIO documentation] or pass:[<emphasis><ulink role="orm:hideurl" url="http://shop.oreilly.com/product/9780596002886.do">Java NIO</ulink></emphasis>] by Ron Hitchens (O'Reilly).
123+
library, see the http://bit.ly/javadoc-nio[Java NIO documentation] or pass:[<emphasis><ulink role="orm:hideurl" url="http://shop.oreilly.com/product/9780596002886.do">Java NIO</ulink></emphasis>] by Ron Hitchens (O'Reilly).
124124

125125
- The Clojure library https://github.com/geoffsalmon/bytebuffer[+bytebuffer+] provides a
126126
thin, more idiomatic wrapper for +ByteBuffer+ operations.

0 commit comments

Comments
 (0)