From ed0e98b305fe0ed7fd108c011e563bfef2eb36ec Mon Sep 17 00:00:00 2001 From: Matthias Felleisen Date: Sun, 3 May 2015 09:25:50 -0400 Subject: [PATCH] Robby's improvement for Jay's things --- pkgs/racket-doc/scribblings/style/some-performance.scrbl | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/pkgs/racket-doc/scribblings/style/some-performance.scrbl b/pkgs/racket-doc/scribblings/style/some-performance.scrbl index d560f8be39..5e7efd93a5 100644 --- a/pkgs/racket-doc/scribblings/style/some-performance.scrbl +++ b/pkgs/racket-doc/scribblings/style/some-performance.scrbl @@ -63,9 +63,11 @@ corresponding to either @racket[library/base] or @racket[library/full].} @item{@racket[library/full], the full library functionality.} ] -If all Racket developers use similar names and think deeply about these -decisions, we can make it easier for Racket users to make wise dependency -decisions. +Keep two considerations in mind as you decide which parts of your library +should be in which files: dependency and logical ordering. The smaller +files should depend on fewer dependencies. Try to organize the levels so +that, in principle, the larger libraries can be implemented in terms of the +public interfaces of the smaller ones. Finally, the advice of the previous section, to use @rkt/base[] when building a library, generalizes to other libraries: by being more