[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: scratch/accurate-warning-pos: next steps.
From: |
Stefan Monnier |
Subject: |
Re: scratch/accurate-warning-pos: next steps. |
Date: |
Tue, 11 Dec 2018 17:58:54 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
> The one Paul and I have been referring to was the one where the reader
> would return extended lists containing location info alongside the
> actual Lisp Object.
This is probably a good option in the long run. But let there be no
doubt: whlie it should not impact performance of compiled code, it will
likely slow down compilation significantly, just because of the
increased size of the representation of the code that the compiler needs
to manipulate.
Stefan
- Re: scratch/accurate-warning-pos: next steps., (continued)
- Re: scratch/accurate-warning-pos: next steps., Paul Eggert, 2018/12/10
- Re: scratch/accurate-warning-pos: next steps., Alan Mackenzie, 2018/12/11
- Re: scratch/accurate-warning-pos: next steps., Paul Eggert, 2018/12/11
- Re: scratch/accurate-warning-pos: next steps., Alan Mackenzie, 2018/12/11
- Re: scratch/accurate-warning-pos: next steps., Paul Eggert, 2018/12/11
- Re: scratch/accurate-warning-pos: next steps., Alan Mackenzie, 2018/12/11
- Re: scratch/accurate-warning-pos: next steps., Stefan Monnier, 2018/12/11
- Re: scratch/accurate-warning-pos: next steps., Alan Mackenzie, 2018/12/11
- Re: scratch/accurate-warning-pos: next steps.,
Stefan Monnier <=
- Re: scratch/accurate-warning-pos: next steps., Paul Eggert, 2018/12/11