From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: why are there [v e c t o r s] in Lisp?
Date: Sun, 18 Oct 2015 14:32:51 +0200 [thread overview]
Message-ID: <87a8rgqrv0.fsf@debian.uxu> (raw)
In-Reply-To: 87fv19asrn.fsf@kuiper.lan.informatimago.com
"Pascal J. Bourguignon" <pjb@informatimago.com>
writes:
> Because the presence of a data type in a language is
> unrelated to the presence of a syntax for literal
> objects of that type. ...
>
> So all the combinations are possible, which shows
> that having a literal syntax for objects and having
> types in a language are two totally
> unrelated things.
They are two different things but they are not
unrelated. If a language offers features A, B, and C,
then it should come in with a syntax a, b, and c to
facilitate the usage of them features.
> Type inference can still be useful in a lisp
> compiler, since it allows to produce code that is
> a little more efficient: you can avoid generating
> type dispatches and type checks in expressions using
> a variable, when you can infer that this variable
> will always hold values of a certain type.
>
> For inference, writing
>
> (let ((a (vector 1 2 3))) (aref a 2))
>
> (let ((a [1 2 3])) (aref a 2))
>
> have the exact same effect: in both case the
> compiler can infer that a is always bound to
> a vector of 3 elements, and therefore it can avoid
> testing whether 2 is bigger or smaller than the size
> of the vector, or that the value bound to a is
> indeed a vector before calling aref.
Inference can be based on the methods used to interact
with the object of the variable. For example the
predicates. If there is an `if' form with a predicate
test for a string (`stringp') and then an `error' if
the variable doesn't hold the string, depending on the
context and the sophistication of the inference
mechanism, it can be deducted the function should be
used with a string as value for a particular argument.
But again this is nothing I ever yearned for...
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2015-10-18 12:32 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.428.1444957396.7904.help-gnu-emacs@gnu.org>
2015-10-16 1:51 ` why are there [v e c t o r s] in Lisp? Pascal J. Bourguignon
2015-10-16 2:31 ` Emanuel Berg
2015-10-16 2:29 ` Random832
2015-10-16 2:51 ` Emanuel Berg
2015-10-16 2:56 ` Random832
2015-10-16 23:30 ` Emanuel Berg
[not found] ` <mailman.482.1445037713.7904.help-gnu-emacs@gnu.org>
2015-10-17 1:55 ` Pascal J. Bourguignon
2015-10-17 4:47 ` Emanuel Berg
[not found] ` <mailman.494.1445057637.7904.help-gnu-emacs@gnu.org>
2015-10-17 15:25 ` Pascal J. Bourguignon
2015-10-17 21:12 ` Emanuel Berg
[not found] ` <mailman.519.1445115776.7904.help-gnu-emacs@gnu.org>
2015-10-18 1:08 ` Pascal J. Bourguignon
[not found] ` <mailman.432.1444964227.7904.help-gnu-emacs@gnu.org>
2015-10-16 3:57 ` Pascal J. Bourguignon
2015-10-16 4:17 ` Random832
[not found] ` <mailman.434.1444970033.7904.help-gnu-emacs@gnu.org>
2015-10-16 5:16 ` Pascal J. Bourguignon
[not found] ` <mailman.429.1444962165.7904.help-gnu-emacs@gnu.org>
2015-10-16 3:31 ` Pascal J. Bourguignon
2015-10-16 23:46 ` Emanuel Berg
[not found] ` <mailman.483.1445038647.7904.help-gnu-emacs@gnu.org>
2015-10-17 2:04 ` Pascal J. Bourguignon
2015-10-17 4:40 ` Random832
2015-10-17 5:00 ` Emanuel Berg
2015-10-17 4:40 ` Emanuel Berg
[not found] ` <mailman.491.1445056308.7904.help-gnu-emacs@gnu.org>
2015-10-17 5:53 ` Barry Margolin
2015-10-17 15:16 ` Pascal J. Bourguignon
2015-10-17 21:06 ` Emanuel Berg
[not found] ` <mailman.518.1445115463.7904.help-gnu-emacs@gnu.org>
2015-10-18 1:07 ` Pascal J. Bourguignon
2015-10-18 12:32 ` Emanuel Berg [this message]
[not found] ` <mailman.551.1445171034.7904.help-gnu-emacs@gnu.org>
2015-10-18 12:55 ` Pascal J. Bourguignon
2015-10-18 14:28 ` Emanuel Berg
2015-10-18 21:17 ` Robert Thorpe
[not found] ` <mailman.557.1445177952.7904.help-gnu-emacs@gnu.org>
2015-10-18 19:48 ` Barry Margolin
2015-10-18 21:25 ` Emanuel Berg
2015-10-18 21:39 ` Random832
2015-10-19 0:46 ` Pascal J. Bourguignon
2015-10-17 5:56 ` Barry Margolin
2015-10-17 15:06 ` Emanuel Berg
2015-10-16 13:32 ` Barry Margolin
2015-10-16 23:47 ` Emanuel Berg
[not found] <mailman.581.1445203060.7904.help-gnu-emacs@gnu.org>
2015-10-19 0:45 ` Pascal J. Bourguignon
2015-10-16 1:12 Emanuel Berg
2015-10-17 1:11 ` Aurélien Aptel
2015-10-17 4:22 ` Emanuel Berg
2015-10-17 7:58 ` Jude DaShiell
2015-10-19 16:33 ` Nick Dokos
[not found] ` <mailman.490.1445055179.7904.help-gnu-emacs@gnu.org>
2015-10-17 15:09 ` Pascal J. Bourguignon
[not found] ` <mailman.488.1445044303.7904.help-gnu-emacs@gnu.org>
2015-10-17 2:22 ` Pascal J. Bourguignon
2015-10-17 4:56 ` Emanuel Berg
2015-10-17 5:49 ` Barry Margolin
2015-10-17 15:04 ` Emanuel Berg
[not found] ` <mailman.506.1445093727.7904.help-gnu-emacs@gnu.org>
2015-10-17 15:20 ` Pascal J. Bourguignon
2015-10-17 15:38 ` Emanuel Berg
[not found] ` <mailman.511.1445095810.7904.help-gnu-emacs@gnu.org>
2015-10-17 16:01 ` Javier
2015-10-17 16:03 ` Javier
2015-10-17 16:34 ` Pascal J. Bourguignon
2015-10-17 21:18 ` Emanuel Berg
2015-10-17 16:15 ` Pascal J. Bourguignon
2015-10-17 21:37 ` Emanuel Berg
2015-10-17 15:18 ` Pascal J. Bourguignon
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=87a8rgqrv0.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--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).