From: Maxime Devos <maximedevos@telenet.be>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>,
mcsinyx@disroot.org, guix-devel@gnu.org
Subject: Re: Strategy for Zig packages
Date: Tue, 26 Jul 2022 21:23:14 +0200 [thread overview]
Message-ID: <07497833-e547-f100-cd15-5e4cef1befbc@telenet.be> (raw)
In-Reply-To: <e8768f226059f80f564ff382aa754dcc0e70302a.camel@gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 979 bytes --]
On 26-07-2022 20:48, Liliana Marie Prikler wrote:
> 4. Convince Zig maintainers to perhaps maybe not join the ranks of Rust
> et al. and produce reusable shared libraries?
I'd like to clarify that Rust supports shared libraries (*) just fine,
it's Cargo that insists on source code.
Looking at
<https://gist.github.com/matu3ba/92e5df1166c51b3725dbd04f7ff1cb4e>, it
might be similar with Zig, as that page is about 'the Zig caching
system' and mentions Zir code, ABIs and objects.
(*) or, at least, rustc's version of static libraries, I haven't tested
out shared libraries yet except for the first failed attempt; there
might be problems with monomorphisation and macros or somehing. Some
libraries, e.g. recent versions of rust-nom, also are written in such a
way that appears to require LTO optimisation to be efficient, which
appears to be non-trivial to be compatible with shared libraries without
extra disk space.
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-07-26 19:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 10:56 Strategy for Zig packages mcsinyx
2022-07-26 18:48 ` Liliana Marie Prikler
2022-07-26 19:23 ` Maxime Devos [this message]
2022-08-01 20:43 ` Mája Tomášek
2022-08-02 5:21 ` mcsinyx
2022-08-02 9:09 ` Maxime Devos
2022-08-03 3:35 ` mcsinyx
2022-08-04 23:56 ` Maxime Devos
2022-08-02 9:11 ` Maxime Devos
2022-08-02 9:01 ` Maxime Devos
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=07497833-e547-f100-cd15-5e4cef1befbc@telenet.be \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=mcsinyx@disroot.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/guix.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).