unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Christine Lemmer-Webber <cwebber@dustycloud.org>
To: Damien Mattei <damien.mattei@gmail.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Guile Steel: a proposal for a systems lisp
Date: Sun, 07 Aug 2022 16:17:57 -0400	[thread overview]
Message-ID: <87czdbkdns.fsf@dustycloud.org> (raw)
In-Reply-To: <CADEOadctuQ2L17diuCQh7BMnj7r6WfrdJxK7AQBeaiZe5ukPLw@mail.gmail.com>


Damien Mattei <damien.mattei@gmail.com> writes:

> On Sun, Aug 7, 2022 at 2:44 PM Christine Lemmer-Webber <cwebber@dustycloud.org> wrote:
>
>  Bigloo is cool.  I think it falls under the same category of Chicken,
>  which I address towards the end of:
>
>    https://dustycloud.org/blog/guile-steel-smelting-pot/
>
>  "Chicken Scheme compiles to C but doesn't strike me as qualifying for
>  this post's vague definition because it still has the usual
>  memory/dynamic typing overheads of Scheme. But go ahead and read
>  literally everything on more-magic.net anyway because that stuff is
>  great."
>
>  Same feels like it could be said of Bigloo, but if I'm wrong, lmk :)
>
> perhaps i'm wrong, but Chicken seems to have strict types as options:
> http://wiki.call-cc.org/man/5/Types

Interesting.  Any examples of it in action, personal use experience,
etc?  I wonder how it handles the famous challenges of keeping that
safety between both statically typed and dynamically typed parts, which
turned out to be extremely expensive, far more than dynamic scoping,
in Racket: https://www2.ccs.neu.edu/racket/pubs/popl16-tfgnvf.pdf
(though there is work being done to make it better, hopefully...
it may have progressed a lot since I last looked, probably has.)

> about Bigloo the best answer would be to ask to author himself but i
> used Bigloo a little to produce JVM class files only, not C obj files,
> and it can be declared some statically typed variable i think in both
> C and Java targets:
> see: 
> https://www-sop.inria.fr/mimosa/fp/Bigloo/manual.html#G82
> and mostly:
> https://www-sop.inria.fr/mimosa/fp/Bigloo/manual-chapter25.html
> Regards,
> Damien

Hm... "Warning: All type annotations are ignored by the interpreter."

>  
>  Damien Mattei <damien.mattei@gmail.com> writes:
>
>  > perhaps Bigloo a Scheme that targets C and has many other features can help:
>  > https://www-sop.inria.fr/mimosa/fp/Bigloo/
>  > Damien
>  >
>  > On Sat, Jul 9, 2022 at 5:38 PM Christine Lemmer-Webber <cwebber@dustycloud.org> wrote:
>  >
>  >  A little blogpost this morning, not actual software, but software
>  >  desiderata:
>  >    https://dustycloud.org/blog/guile-steel-proposal/
>  >
>  >  I'd love to see something like the above happen.  I'd love to help make
>  >  it happen.  So this is more of a call to arms than anything else.
>  >
>  >  Can we have a "systems lisp"?  Can we do better than Rust?  Let's put
>  >  some interesting things on that compiler tower of ours!




  parent reply	other threads:[~2022-08-07 20:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-09 15:35 Guile Steel: a proposal for a systems lisp Christine Lemmer-Webber
2022-07-10  9:46 ` Blake Shaw
2022-07-10 12:14 ` Zelphir Kaltstahl
2022-07-11 11:13 ` Tim Van den Langenbergh
2022-07-15 12:08   ` Christine Lemmer-Webber
2022-08-06 22:38     ` Christine Lemmer-Webber
2022-07-11 13:10 ` Martin Becze
2022-08-07  9:28 ` Damien Mattei
2022-08-07 12:43   ` Christine Lemmer-Webber
2022-08-07 14:47     ` Damien Mattei
2022-08-07 16:02       ` Andrew Gwozdziewycz
2022-08-07 20:17       ` Christine Lemmer-Webber [this message]
2022-08-07 21:12         ` Damien Mattei

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/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87czdbkdns.fsf@dustycloud.org \
    --to=cwebber@dustycloud.org \
    --cc=damien.mattei@gmail.com \
    --cc=guile-user@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.
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).