aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2017-09-21 23:05:39 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2017-09-21 23:05:39 +0200
commit72b93a2e89bebdf7b864c0105f6b427f45d484f0 (patch)
tree4e07dda1af4ad4eb718facb902bde0b8d308fed2 /doc
parent1ce0963557a8bbd61ca27cc448f459ba8ceaee56 (diff)
Minor doc clarification
Diffstat (limited to 'doc')
-rw-r--r--doc/manual.cli6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/manual.cli b/doc/manual.cli
index 5d6ef08..63929f9 100644
--- a/doc/manual.cli
+++ b/doc/manual.cli
@@ -1467,9 +1467,9 @@ fairly large \c{std.core} and \c{std.io} modules.
There is, however, a significant drawback to this choice: every time we make a
change, all consumers of such a mega-module will have to be recompiled,
whether the change affects them or not. And the bigger the module the higher
-the chance that any given change does not affect a large portion of the
-module's consumers. Note also that this is not an issue for the standard
-library modules since they are not expected to change often.
+the chance that any given change does not (semantically) affect a large
+portion of the module's consumers. Note also that this is not an issue for the
+standard library modules since they are not expected to change often.
Another, more subtle, issue with mega-modules (which does affect the standard
library) is the inability to re-export only specific interfaces, as will be