From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: url-retrieve fails on most HTTPS sites
Date: Tue, 29 Sep 2020 12:32:45 +0200 [thread overview]
Message-ID: <20200929103245.GD31698@tuxteam.de> (raw)
In-Reply-To: <87eemkrjzg.fsf@ebih.ebihd>
[-- Attachment #1: Type: text/plain, Size: 1559 bytes --]
On Tue, Sep 29, 2020 at 11:49:07AM +0200, Emanuel Berg via Users list for the GNU Emacs text editor wrote:
> tomas wrote:
>
> > Things become more interesting if the thing coming
> > after #' is a symbol, like in #'car.
>
> The use case, at least mine, is to denote functions
> so the byte-compiler can check if they are defined.
> Makes development faster and more pleasant...
>
> Yeah ... what _is_ the origin/reason of this thing,
> deep down? That symbols are not only a value or
> a function but both, and more?
>
> symbol-function
> symbol-value
> ...
Exactly.
> > Then we all know we are talking about car's
> > symbol-function. This allows the human code readers
> > and the compiler to be smarter about the code.
>
> Yeah, however what gain is there to mucking with
> that? That cannot be solved, or solved in a worse
> way, with "dedicated symbols", I guess?
Well, #' is just a shorthand for function, just as ' is a
shorthand for quote.
If you do #'car (or, what's the same (function car)), the
compiler can, for example, warn you early that there's no
function named like this (for the symbol car, your Lisp would
be... in a strange state, but you get the idea :)
Plus lots of other optimizations the compiler can do if it
knows that it's the function value you are talking about.
Plus the clarity of your code for your other readers.
All of that isn't necessary for (lambda (...) ...), since
it's lambda's job to make functions. We know that, the
compiler knows that.
Cheers
- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2020-09-29 10:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 20:41 url-retrieve fails on most HTTPS sites Nicolas Graner
2020-09-28 23:13 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-28 23:24 ` 2QdxY4RzWzUUiLuE
2020-09-28 23:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29 2:26 ` Stefan Monnier
2020-09-29 3:24 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29 9:31 ` tomas
2020-09-29 9:49 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29 10:32 ` tomas [this message]
2020-09-29 10:50 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29 14:14 ` Sharp--quote [was: url-retrieve fails on most HTTPS sites] tomas
2020-09-29 14:56 ` Stefan Monnier
2020-09-29 15:19 ` tomas
2020-09-29 16:03 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29 16:01 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29 15:18 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29 3:45 ` url-retrieve fails on most HTTPS sites 황병희
2020-09-29 2:50 ` 2QdxY4RzWzUUiLuE
2020-09-29 5:45 ` Colin Baxter
2020-09-29 11:29 ` 2QdxY4RzWzUUiLuE
2020-09-29 13:57 ` Colin Baxter
2020-09-29 14:53 ` HTTPS fails (was: url-retrieve fails on most HTTPS sites) Nicolas Graner
2020-09-29 15:10 ` Nicolas Graner
2020-09-29 15:16 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-09-29 14:47 ` url-retrieve fails on most HTTPS sites Noam Postavsky
2020-09-29 15:08 ` Nicolas Graner
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=20200929103245.GD31698@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-gnu-emacs@gnu.org \
/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.
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).