[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Declaim and proclaim
From: |
Stefan Monnier |
Subject: |
Re: Declaim and proclaim |
Date: |
Wed, 23 Apr 2014 09:14:16 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (gnu/linux) |
>>> That test was there in cl-check-type. The test doesn't make sense to me
>>> either. We should drop it in both places if we drop it in cl-the.
>> Great, let's drop it then. Thanks.
> On second thought, I'm not sure it's so simple. First of all, nobody in
> the tree actually changes the default speed or safety settings, AFAICT.
Could you explain what this discussion has to do with the
removal of the cl--compiling-file calls?
> sure we should change how it works now without having a discussion of
> how we want this whole system to work.
It's not terribly important, tho. Given the simplicity of the
implementation techniques we use, this CL optimization infrastructure is
over-engineered.
> Should we make cl--optimize-speed and cl--optimize-safety buffer-local?
> And shouldn't we be setting the default values to 3 and 0, respectively,
> during initial Emacs compilation when we haven't been given configured
> with --enable-checking?
What would that change?
> Also, we could make cl-locally do something useful by having it bind
> cl--optimize-speed and cl--optimize-safety, then fully macroexpand its body.
Not worth the trouble, methinks.
Stefan