Re: [VM] Should `compile' always be visible?

[Ludovic Courtès]

Hello!

Andy Wingo <address@hidden> writes:

> On Fri 20 Feb 2009 01:45, address@hidden (Ludovic Courtès) writes:
>
>> Do we really need it?  Guile `master' doesn't put any autoload in the
>> global namespace, only in `guile-user-module', thus only affecting the
>> REPL.
>
> Yeah, dunno. It would be great to have `compile' in the toplevel
> environment. OTOH it takes time.

Just to be clear: I wasn't so much concerned about load time, but rather
about namespace pollution and fuzzy dependencies ("ambient authority").
Why add yet another set of global bindings if we can avoid it?

> This is all on my laptop running at full speed, an average over 10 runs.

Is it when running `pre-inst-guile', the Libtool-generated `guile'
script, or the raw `guile' executable?

> I would like for the base language to include syncase. I think it's
> worth paying 6 ms. But I would keep compile as autoload, or explicitly
> included, until other things speed up. Maybe a useful goal would be:
> always be faster than Python, just because we can :-)

Eh eh!  I agree that `syncase' should be loaded by default now that we
no longer have to worry about its execution time.

Thanks,
Ludo'.