From: Alex Gramiak <agrambot@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [RFC] Some new vector procedures (vector-{memq, apply, to-string, ...})
Date: Sat, 20 Apr 2019 19:52:36 -0600 [thread overview]
Message-ID: <877ebo6s63.fsf@gmail.com> (raw)
In-Reply-To: <83tvesa3w1.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 20 Apr 2019 22:11:10 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Alex Gramiak <agrambot@gmail.com>
>> Cc: emacs-devel@gnu.org
>> Date: Sat, 20 Apr 2019 12:18:01 -0600
>>
>> Ideally. Though in the case of vector-partition the size of the 2
>> partition vectors is not known in advance, so a Lisp implementation
>> would have to create two extra Lisp vectors as opposed to using
>> SAFE_ALLOCA. That is, unless Elisp grows a growable/resizeable vector
>> type (which is something I was thinking about -- would that be denied?).
>
> What would be the advantage of that vs lists?
Better space efficiency, less pressure (hopefully) on the GC, and faster
random access. I believe growable vectors would make sense for linear
lists that don't need the insertion/deletion properties of linked lists.
As for vector-partition, it's more so a means of keeping the input and
partition types the same. Not a huge deal.
> Vectors are used quite rarely in Emacs Lisp, IME.
Not enough suitable vector procedures doesn't help, though. Emacs Lisp
is certainly not a general-purpose language, but that doesn't mean that
it has to be missing particular language features/types that improve
efficiency as long as it doesn't add a lot of complexity.
> Every additional primitive means a burden. More importantly, we
> should IMO be consistent in how we design and implement families of
> functions, which is why I still think we should extend seq.el
> (possibly some of that with internal C primitives, if needed), instead
> of starting a new family.
I'm not sure what you mean here by internal C primitives if it's not
similar to vector-memq/member. Do you just mean expose a single
`sequence-memq' and keep the new type-specific implementations internal?
next prev parent reply other threads:[~2019-04-21 1:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 20:49 [RFC] Some new vector procedures (vector-{memq, apply, to-string, ...}) Alex Gramiak
2019-04-20 7:04 ` Eli Zaretskii
2019-04-20 16:50 ` Alex Gramiak
2019-04-20 17:16 ` Eli Zaretskii
2019-04-20 18:18 ` Alex Gramiak
2019-04-20 19:11 ` Eli Zaretskii
2019-04-20 19:54 ` Alan Mackenzie
2019-04-20 20:09 ` Óscar Fuentes
2019-04-20 22:54 ` Paul Eggert
2019-04-21 3:01 ` Using SMALL_LIST_LEN_MAX for memq and list_length (was: [RFC] Some new vector procedures (vector-{memq, apply, to-string, ...})) Alex Gramiak
2019-04-21 1:52 ` Alex Gramiak [this message]
2019-04-21 5:50 ` [RFC] Some new vector procedures (vector-{memq, apply, to-string, ...}) Eli Zaretskii
2019-04-21 4:05 ` Stefan Monnier
2019-04-21 20:34 ` Alex Gramiak
2019-04-21 21:01 ` Stefan Monnier
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=877ebo6s63.fsf@gmail.com \
--to=agrambot@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.
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).