-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix compilation issues and remove uses of old advice facility #670
base: master
Are you sure you want to change the base?
Changes from 3 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -7,6 +7,9 @@ | |||||
|
||||||
;;; Code: | ||||||
|
||||||
;; FIXME: Merely loading a file should not have such side effects. | ||||||
;; We should move all of that code into a function. | ||||||
|
||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hi @monnier! Line 39 in 8e688a6
Are you fine with this layout? or would you still request a refactoring of these two files? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Side question: would you recommend removing this line, perhaps? ↓ Line 371 in 8e688a6
which has no equivalent at the end of |
||||||
;; Setup MELPA | ||||||
(require 'package) | ||||||
(setq gnutls-algorithm-priority "NORMAL:-VERS-TLS1.3") | ||||||
|
@@ -24,7 +27,10 @@ | |||||
(unless (package-installed-p 'ert-async) | ||||||
(package-refresh-contents) | ||||||
(package-install 'ert-async)) | ||||||
|
||||||
(eval-when-compile | ||||||
(require 'ert-async)) | ||||||
;; FIXME: Why do we have this `require' and why is it within | ||||||
;; an `eval-when-compile'? | ||||||
(require 'ert-async nil t)) | ||||||
|
||||||
;;; init-tests.el ends here |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @monnier !
I am a aware that indeed, adding
lexical-binding
as soon as possible is a good rule-of-thumb if we can.But just to name a potential issue, we had found some months ago when discussing in our regular PG telco that when you had enabled this mode everywhere in the code maintained by @hendriktews, the lexical-binding had broken some invariants :-/ (in some subtle cases I don't remember now)
And even I'm not fully savvy of all the implications of this mode, I just wanted to raise this point and say that maybe, it'd be wise not to add it blindly without some additional discussion…
So @monnier, could you try to summarize all the pros and cons of adding it?
Anyway, thanks for proposing this PR 👍