Re: Time to merge scratch/correct-warning-pos into master, perhaps?

[Lars Ingebrigtsen]

Alan Mackenzie <acm@muc.de> writes:

> By doing something like calling read rather than read-positioning-symbols
> from the byte compiler, and putting conditional compilation into
> lisp_h_EQ, etc., in src/lisp.h?  This would leave the compiler not fully
> functional, of course.  It might work.

Or just have conditional compilation of lisp_h_EQ and have
read-positioning-symbols be an alias for read (when this is disabled).
Or something like that.  So the code impact of the configuration option
could be very localised.

> I would more favour the slightly more laborious strategy: benchmark on
> the master branch in two repositories, one just before the big merge, the
> other just after.

People don't like to skip back in git history much, because other code
has also moved on since that time, and you end up with various obscure
issues very fast.  Configuration options are just more handy.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no