From: Arvydas Silanskas <nma.arvydas.silanskas@gmail.com>
To: kawa mailing list <kawa@sourceware.org>
Subject: srfi 145
Date: Thu, 29 Sep 2022 10:48:03 +0300 [thread overview]
Message-ID: <CAPh7weCzfAjddpAf8zBRqrabT4e8feoSkgE1cCgv-ScCHBA5AQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 780 bytes --]
Good day,
what are your opinions on srfi 145? Looking at it, it could be a decent
r7rs portable way to provide some degree of static type checking. The work
would involve adding a syntax tree rewrite pass. For example, code such as
(define (foo a)
(assume (integer? a))
...)
would be transformed to
(define (foo a ::int)
...)
and then the rest of it would be usual kawa behavior. Certainly making it
as powerful as a standard kawa syntax would be very difficult, but perhaps
it's not necessary? I think handling only function parameters + let
bindings, and only handling base types + user defined simple records would
pragmatically cover a lot of useful cases.
If there is a consensus that this would be useful, I'll give it a shot at
implementing it myself.
Arvydas
reply other threads:[~2022-09-29 7:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPh7weCzfAjddpAf8zBRqrabT4e8feoSkgE1cCgv-ScCHBA5AQ@mail.gmail.com \
--to=nma.arvydas.silanskas@gmail.com \
--cc=kawa@sourceware.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).