unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip McGrath <philip@philipmcgrath.com>
To: 46865@debbugs.gnu.org
Subject: [bug#46865] [PATCH] gnu: racket: update to 8.0.
Date: Wed, 3 Mar 2021 10:06:14 -0500	[thread overview]
Message-ID: <98899839-7ce4-28a6-28c0-a215780e698d@philipmcgrath.com> (raw)
In-Reply-To: <20210302004318.26523-1-philip@philipmcgrath.com>

I changed the description primarily because, as of Racket 8.0, it is no 
longer accurate to say, "It features a compiler and a virtual machine 
with just-in-time native compilation"—the default implementation is now 
a native code compiler based on Chez Scheme.

But there's certainly still room for improvement. In particular, I see 
that Nix is using the description:

 > Racket is a full-spectrum programming language. It goes beyond
 > Lisp and Scheme with dialects that support objects, types,
 > laziness, and more. Racket enables programmers to link
 > components written in different dialects, and it empowers
 > programmers to create new, project-specific dialects. Racket's
 > libraries support applications from web servers and databases to
 > GUIs and charts.

The Racket project has used descriptions along those lines in other 
places before.

I left the synopsis, "Implementation of Scheme and related languages", 
alone, but that's also debatable. From a Racketeer's perspective,
Racket contains a Scheme implementation, but it is not primarily a 
Scheme implementation. Nix uses the short description, "A programmable 
programming language".




  reply	other threads:[~2021-03-03 16:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02  0:43 [bug#46865] [PATCH] gnu: racket: update to 8.0 Philip McGrath
2021-03-03 15:06 ` Philip McGrath [this message]
2021-03-05 11:49 ` bug#46865: " Ludovic Courtès
2021-03-05 13:35   ` [bug#46865] " Philip McGrath
2021-03-05 16:06     ` Jack Hill
2021-03-08 14:33     ` Ludovic Courtès
2021-03-05 13:49   ` Christopher Lemmer Webber

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=98899839-7ce4-28a6-28c0-a215780e698d@philipmcgrath.com \
    --to=philip@philipmcgrath.com \
    --cc=46865@debbugs.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.
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).