From: Lynn Winebarger <owinebar@gmail.com>
To: Jonas Bernoulli <jonas@bernoul.li>
Cc: Philip Kaludercic <philipk@posteo.net>,
Yuan Fu <casouri@gmail.com>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Unboxed package manager
Date: Wed, 22 Mar 2023 19:39:27 -0400 [thread overview]
Message-ID: <CAM=F=bATeBuMLkuYCVR8m6WPOrbrbTDpjD3N1MWvp1ojS6yTPA@mail.gmail.com> (raw)
In-Reply-To: <CAM=F=bDttt1mVLR5fYbkdELK3ik_HoQ0Q7VMW=7yY38xjdF2jQ@mail.gmail.com>
On Wed, Mar 22, 2023 at 10:31 AM Lynn Winebarger <owinebar@gmail.com> wrote:
> It's not the SQL expressions I'm concerned about. I'm just thinking of the existing sql-using code base expects rows to be represented with arrays, why add the cost of remarshalling them from lists?
>
> It just seems like a gratuitous incompatibility to me, unless there's a strong reason to prefer lists. I have no other reason to prefer either representation. The die is cast now, anyway.
I did think of one other hackish (possibly kludgish) reason to return
arrays rather than lists. It makes storing/returning collections of
structs (as currently implemented, anyway) to/from rows very low
overhead, at least if there is a way to store LispObjects
transparently. There isn't a way to do so currently, of course.
Lynn
next prev parent reply other threads:[~2023-03-22 23:39 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 1:18 Unboxed package manager Lynn Winebarger
2023-03-20 6:30 ` Yuan Fu
2023-03-20 8:55 ` Lynn Winebarger
2023-03-20 9:09 ` Lynn Winebarger
2023-03-20 15:25 ` Philip Kaludercic
2023-03-20 16:12 ` Lynn Winebarger
2023-03-20 16:53 ` Philip Kaludercic
2023-03-20 18:11 ` Jonas Bernoulli
2023-03-21 1:40 ` Lynn Winebarger
2023-03-22 11:17 ` Jonas Bernoulli
2023-03-22 14:31 ` Lynn Winebarger
2023-03-22 23:39 ` Lynn Winebarger [this message]
2023-03-21 19:06 ` Augusto Stoffel
2023-03-21 19:10 ` Philip Kaludercic
2023-03-21 19:57 ` Augusto Stoffel
2023-03-21 20:06 ` Philip Kaludercic
2023-03-21 0:23 ` Gregory Heytings
2023-03-21 0:25 ` Gregory Heytings
2023-03-21 1:55 ` Lynn Winebarger
2023-03-21 10:36 ` Lynn Winebarger
2023-03-21 10:52 ` Gregory Heytings
2023-03-21 13:23 ` Eli Zaretskii
2023-03-21 13:33 ` Gregory Heytings
2023-03-21 14:13 ` Eli Zaretskii
2023-03-21 14:20 ` Gregory Heytings
2023-03-21 17:29 ` Eli Zaretskii
2023-03-22 0:48 ` Lynn Winebarger
2023-03-22 14:42 ` Eli Zaretskii
2023-03-22 22:22 ` Lynn Winebarger
2023-03-23 6:46 ` Eli Zaretskii
2023-03-23 13:30 ` Lynn Winebarger
2023-03-24 17:54 ` chad
2023-03-26 1:51 ` Lynn Winebarger
2023-03-23 1:44 ` David Masterson
2023-03-23 7:02 ` Eli Zaretskii
2023-03-22 7:29 ` tomas
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='CAM=F=bATeBuMLkuYCVR8m6WPOrbrbTDpjD3N1MWvp1ojS6yTPA@mail.gmail.com' \
--to=owinebar@gmail.com \
--cc=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jonas@bernoul.li \
--cc=philipk@posteo.net \
/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).