From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How does `describe-function' know where the source code of the function is?
Date: Tue, 18 Jan 2022 13:46:25 -0500 [thread overview]
Message-ID: <jwvsftkopfu.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87ee55eybe.fsf@mbork.pl> (Marcin Borkowski's message of "Tue, 18 Jan 2022 18:41:25 +0100")
> Thanks! This is actually kind of fascinating - on the one hand, it
> seems so fragile, and on the other hand, it works 99.99% of the time...
It's actually the result of a form of machine learning: when the system
fails to work, we get a bug-report which feeds back into improving the
system, so with enough users using the system that gets up millions of
"training data".
The backpropagation algorithm involves actual human brain cells, tho ;-)
Stefan
prev parent reply other threads:[~2022-01-18 18:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 4:03 How does `describe-function' know where the source code of the function is? Marcin Borkowski
2022-01-17 4:14 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-17 4:27 ` Eduardo Ochs
2022-01-17 16:22 ` Michael Heerdegen
2022-01-18 2:51 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-01-18 17:41 ` Marcin Borkowski
2022-01-18 18:46 ` Stefan Monnier [this message]
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=jwvsftkopfu.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=help-gnu-emacs@gnu.org \
--cc=mbork@mbork.pl \
/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).