unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "(" <paren@disroot.org>
To: "Wojtek Kosior" <koszko@koszko.org>
Cc: <guix-devel@gnu.org>
Subject: Re: Struggling to write Dissecting Guix, Part 2
Date: Thu, 26 Jan 2023 06:33:27 +0000	[thread overview]
Message-ID: <CQ1WUPNSVXO6.20FL76ZIJC2EU@guix-framework> (raw)
In-Reply-To: <20230125165445.24771f77.koszko@koszko.org>

[-- Attachment #1: Type: text/plain, Size: 441 bytes --]

On Wed Jan 25, 2023 at 3:54 PM GMT, Wojtek Kosior wrote:
> While Guile is dynamically typed, functions we define in it generally
> do expect their arguments to be of certain types. And they also
> generally guarantee their return values to be of certain types. So even
> though there's no static type checking, it is still possible (and often
> practical) to treat the functions as being typed.

I suppose that's true :)

    -- (

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2023-01-26  6:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-25  7:12 Struggling to write Dissecting Guix, Part 2 (
2023-01-25  9:58 ` zimoun
2023-01-26  6:32   ` (
2023-01-25 15:54 ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2023-01-26  6:33   ` ( [this message]
2023-01-26 11:17   ` Simon Tournier
2023-01-26 20:03     ` bokr
2023-01-27 11:50       ` Simon Tournier
2023-01-25 19:39 ` david larsson
2023-01-26  6:34   ` (
2023-01-28 18:28     ` david larsson
2023-01-26 20:45 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.

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=CQ1WUPNSVXO6.20FL76ZIJC2EU@guix-framework \
    --to=paren@disroot.org \
    --cc=guix-devel@gnu.org \
    --cc=koszko@koszko.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).