diff options
| author | Eelco Dolstra <e.dolstra@tudelft.nl> | 2004-01-08T15·01+0000 |
|---|---|---|
| committer | Eelco Dolstra <e.dolstra@tudelft.nl> | 2004-01-08T15·01+0000 |
| commit | b5942155314ea4b479fabde6ce236866f5ef4b97 (patch) | |
| tree | 798889a5b7fb696dc6eafbdbdf732cd493e0e5fc /doc/manual/bugs.xml | |
| parent | 5346536b626a047d53f9c44d6562cfaeffe27f14 (diff) | |
* Manual updates.
Diffstat (limited to 'doc/manual/bugs.xml')
| -rw-r--r-- | doc/manual/bugs.xml | 30 |
1 files changed, 13 insertions, 17 deletions
diff --git a/doc/manual/bugs.xml b/doc/manual/bugs.xml index fcb69c3641a5..33bd96a02de4 100644 --- a/doc/manual/bugs.xml +++ b/doc/manual/bugs.xml @@ -5,24 +5,20 @@ <listitem> <para> - Nix should automatically remove Berkeley DB logfiles. - </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 + 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 closure expression is more efficient + that realising the derivation expression from which it 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. + 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> |