From: Andrea Corallo <akrl@sdf.org>
To: Sebastian Sturm <mail@sebastian-sturm.de>
Cc: 42088@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#42088: [feature/native-comp] Lockup on opening TypeScript files
Date: Sun, 28 Jun 2020 10:43:22 +0000 [thread overview]
Message-ID: <xjfk0zrsc6t.fsf@sdf.org> (raw)
In-Reply-To: <xjfzh8oryjd.fsf@sdf.org> (Andrea Corallo's message of "Sat, 27 Jun 2020 21:25:58 +0000")
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.
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.
===
(require 'cl-lib)
(defun foo ()
(cl-loop for xxx in '(a b)
for yyy = xxx
do (print xxx)))
===
This fails only compiling for dynamic scope because in lexical all
--cl-vars-- are absorbed as slots in the execution stack.
I suspect the solution is to have some renaming performed by the native
compiler not to confuse them.
Andrea
--
akrl@sdf.org
next prev parent reply other threads:[~2020-06-28 10:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-27 16:55 bug#42088: [feature/native-comp] Lockup on opening TypeScript files Sebastian Sturm
2020-06-27 21:25 ` Andrea Corallo
2020-06-28 10:43 ` Andrea Corallo [this message]
2020-06-28 20:38 ` Andrea Corallo
2020-06-30 2:33 ` Stefan Monnier
2020-06-30 8:06 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-06-30 14:03 ` Stefan Monnier
2020-06-30 14:43 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-06-29 21:01 ` Sebastian Sturm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xjfk0zrsc6t.fsf@sdf.org \
--to=akrl@sdf.org \
--cc=42088@debbugs.gnu.org \
--cc=mail@sebastian-sturm.de \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).