about summary refs log tree commit diff
path: root/doc/manual/bugs.xml
diff options
context:
space:
mode:
authorEelco Dolstra <e.dolstra@tudelft.nl>2003-08-13T10·45+0000
committerEelco Dolstra <e.dolstra@tudelft.nl>2003-08-13T10·45+0000
commitc34a153ae5614ab879ff19194ff396ffb21b7b55 (patch)
treee1f0236bf4c0046cbd1b71f48e65a9927169bee7 /doc/manual/bugs.xml
parentb4f88d0ec364f00196127ea29e8db5033368e23a (diff)
* Documented the `--query' operation.
Diffstat (limited to 'doc/manual/bugs.xml')
-rw-r--r--doc/manual/bugs.xml17
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/manual/bugs.xml b/doc/manual/bugs.xml
index 33c6e767baca..548ce1cab830 100644
--- a/doc/manual/bugs.xml
+++ b/doc/manual/bugs.xml
@@ -15,6 +15,23 @@
       </para>
     </listitem>
 
+    <listitem>
+      <para>
+	Unify the concepts of successors and substitutes into a general notion
+	of <emphasis>equivalent expressions</emphasis>.  Expressions are
+	equivalent if they have the same target paths with the same
+	identifiers.  However, even though they are functionally equivalent,
+	they may differ stronly with respect to their <emphasis>performance
+	  characteristics</emphasis>.  For example, realising a slice is more
+	efficient that realising the derivation from which that slice was
+	produced.  On the other hand, distributing sources may be more
+	efficient (storage- or bandwidth-wise) than distributing binaries.  So
+	we need to be able to attach weigths or priorities or performance
+	annotations to expressions; Nix can then choose the most efficient
+	expression dependent on the context.
+      </para>
+    </listitem>
+
   </itemizedlist>
 
 </appendix>