memory-leaks

Still reachable: lots of words in many pages.
git clone https://git.kevinlegouguec.net/memory-leaks
Log | Files | Refs | README | LICENSE

commit 0bf6c203d14d669c89ece9515ed5594634c41763
parent f75a4b9c5d131f046ae6ce3d73c4b764a25bdd5f
Author: Kévin Le Gouguec <kevin.legouguec@gmail.com>
Date:   Sun, 27 Sep 2026 10:40:16 +0200

Add reference to Stefan's post-mortem for pure storage

Diffstat:
Mreviews/emacs/hype.org | 4++++
1 file changed, 4 insertions(+), 0 deletions(-)

diff --git a/reviews/emacs/hype.org b/reviews/emacs/hype.org @@ -95,6 +95,10 @@ Nice that we no longer need to figure out which strings to ~purecopy~, that we can always use ~define-key~ and forget about ~bindings--define-key~, that ~defconst~ no longer causes pure-copying hazards… + +See [[https://lists.gnu.org/archive/html/help-gnu-emacs/2026-09/msg00116.html][Stefan Monnier's explanations]] for the historical motivations for +pure storage, and why modern circumstances have made these motivations +obsolete. *** User Lisp directory I have always envied folks who conscientiously break their init file down into modular package-like files: at the time of writing, my own