[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#42088: [feature/native-comp] Lockup on opening TypeScript files
From: |
Stefan Monnier |
Subject: |
bug#42088: [feature/native-comp] Lockup on opening TypeScript files |
Date: |
Tue, 30 Jun 2020 10:03:28 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
>> The printer is normally able to preserve this info (printing #:<foo>
>> instead of <foo> for uninterned symbols and using #= and such the refer
>> to exactly that symbol) when printing code into the .elc file, so I'm
>> wondering why it gets lost when going through the native compiler.
> Yes that's the conclusion I came-up shortly after. Turned out that the
> native compiler was not configuring the printer to handle uninterned
> symbols, so the fix I pushed Sunday:
> 7f8512765a * Setup correctly the printer while dumping objs in native CU
> (bug#42088)
Great thanks!
> I corrected myself and discussed the fix in a mail sent into this thread
> but unfortunately this got lost. My sdf mail lost a number of mails in
> the last days both incoming and out-coming (possibly including one I sent
> you :).
[ Not sure what's the standard euphemism in use in France nowadays but
back when I lived nearby, "SDF" meant "sans domicile fixe" i.e. what we
here call "homeless" (and I've heard it referred to disturbingly as
"rough sleepers"). ]
Stefan
bug#42088: [feature/native-comp] Lockup on opening TypeScript files, Sebastian Sturm, 2020/06/29