[racket-dev] enter! verbosity

From: Carl Eastlund (cce at ccs.neu.edu)
Date: Sat Dec 11 17:07:19 EST 2010

On Sat, Dec 11, 2010 at 4:58 PM, Eli Barzilay <eli at barzilay.org> wrote:
> Yesterday, Jakub Piotr Cłapa wrote:
>> On 10.12.10 21:05, Noel Welsh wrote:
>> > It is moderately useful to see what is reloaded if you renter enter!
>> Just a quick thought:
>> Let it output what it is "reloading" and not what is loaded for the
>> first time. OTOH does enter! really do any reloading?
> That implies at one reason for the verbose loading messages: modules
> that your code depends on do not get reloaded:
>  > (enter! "x")
>   [loading /tmp/x]
>   [loading /home/eli/plt/collects/racket/lang/compiled/reader_rkt.zo]
>   [loading /home/eli/plt/collects/syntax/compiled/module-reader_rkt.zo]
>   [loading /home/eli/plt/collects/syntax/compiled/readerr_rkt.zo]
> ... edit the file ...
>  > (enter! "x")
>   [re-loading /tmp/x]

I can see the usefulness of this output for someone in the process of
developing the language in question, and testing it at the Racket
REPL.  But it's not as useful for just trying out other languages
(e.g. evaluating Typed Racket at the REPL) when they're not going to
change.  Would it be possible to have two versions of the macro, or a
keyword option, or some other way to turn the output on/off as
desired?  Personally, I have used enter! a number of times, and have
never had any use for the pages of output it generates.  Even if I
were developing a language this way, I'm not sure I'd want to see all
that output most of the time -- maybe only if a regular, quiet enter!
behaved oddly and I wanted to debug it.


Posted on the dev mailing list.