[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: |
Mon, 29 Jun 2020 22:33:02 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
> Okay after some digging I think I've an idea of what is going on:
>
> the code was hanging in `typescript--ensure-cache' in the loop
>
> (cl-loop while (re-search-forward typescript--quick-match-re-func nil t)...
>
> This because typescript--quick-match-re-func is not set correctly going
> back and back this is because `typescript--available-frameworks' is set
> to nil.
Hmm... I'm afraid I can't follow this. Could you provide some details?
> IIUC the reason for that is: cl-macs is expanding cl-loop using various
> `--cl-var--', these looks the same but each of this is a separete
> uninterned symbol. The native compiler squash them all toghether having
> to pass them through the reader and a simple testcase like this fails to
> behave as expected.
How/where exactly do they get squashed?
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.
Stefan
bug#42088: [feature/native-comp] Lockup on opening TypeScript files, Sebastian Sturm, 2020/06/29