Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Grammar nitpick: compounded -> compound #1

Open
wants to merge 1 commit into from

1 participant

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Oct 26, 2013
  1. @grig
This page is out of date. Refresh to see the latest.
Showing with 2 additions and 2 deletions.
  1. +2 −2 eeps/eep-0043.md
View
4 eeps/eep-0043.md
@@ -74,7 +74,7 @@ Specification
A map `M` consists of a number of *associations* and keeps an association
from key terms `K1..Kn` to value terms `V1..Vn` where no two keys are *equal*.
-Any term, compounded or otherwise, is a viable key or value. Terms of type Map
+Any term, compound or otherwise, is a viable key or value. Terms of type Map
are recognized by guard tests `erlang:is_map/1`. There are no operators
acting on maps. Within maps there are two infix operators. An association
operator, `=>`, pairs a key to a value and is used in creation and updates.
@@ -1099,7 +1099,7 @@ is given for each question and stems from discussions in this proposal.
implementation.
* The significant difference is the memory overhead in the storing structure.
Since memory overhead for keys and values has the same behavior as in any
- compounded term or abstract data-type, i.e. dict or gb_trees, the main
+ compound term or abstract data-type, i.e. dict or gb_trees, the main
difference occurs when comparing maps to records and frames. To ensure a
logarithmic worst-case performance in update or retrieval some sort tree
structure would likely be used for maps. Maps would then stores keys
Something went wrong with that request. Please try again.