From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] why developers love rust on stackoverflow blog
Date: Wed, 10 Jun 2020 13:06:43 +0100
Message-ID: <CAPweEDxRMgb0ge+uErC+zjepjKtwDKyzk7KqahEvLatyP7Zziw@mail.gmail.com> (raw)
In-Reply-To: <CAC2bXD7hs6uom2a161ikAb_p3HzLsd_WbNoKE+EMwYH5jYdkVw@mail.gmail.com>
On Wed, Jun 10, 2020 at 9:22 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
> I definitely agree, and the lack of good interfaces is one of my biggest
> pain points with Python.
yep. except... in a large well-maintained collaborative and useful
project, you need unit tests, regardless of what language the code is
in.
and if that language is python, well-written and properly
comprehensive unit tests will inherently find you any interface
problems pretty much instantly - just not at compile-time, because
there isn't one [except if you use cython].
and if they're _not_ found, that's indicative of a failure of the
whole team - including the contributing userbase - to write (or
contribute) sufficiently comprehensive unit tests. *not* of the
language itself.
rust, i get it: there's a strong reliance on the compiler, and on the
definition of types, in ways that have not been done in other
langugages. in my mind, the alarm bells there are to imagine that
because the language provides that safety net, therefore
"automatically unit tests are not necessary to write, because the
compiler will catch everything for me".
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 8:21 Jacob Lifshay
2020-06-10 12:06 ` Luke Kenneth Casson Leighton [this message]
2020-06-10 12:44 ` Luke Kenneth Casson Leighton
2020-06-10 15:09 ` Hendrik Boom
2020-06-10 18:24 ` Jacob Lifshay
2020-06-10 21:28 ` Cole Poirier
2020-06-10 22:35 ` Hendrik Boom
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=CAPweEDxRMgb0ge+uErC+zjepjKtwDKyzk7KqahEvLatyP7Zziw@mail.gmail.com \
--to=lkcl@lkcl.net \
--cc=libre-riscv-dev@lists.libre-riscv.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
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git