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:44:46 +0100
Message-ID: <CAPweEDyyM0gyeGj_Aq3_jhokBCQWA_dw7cFaZfNOT-T7Q_J1CQ@mail.gmail.com> (raw)
In-Reply-To: <CAPweEDxRMgb0ge+uErC+zjepjKtwDKyzk7KqahEvLatyP7Zziw@mail.gmail.com>
On Wed, Jun 10, 2020 at 1:06 PM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
> 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.
which has me thinking: is there any way that we could improve things
for python... however _without_ interfering with the code-compactness,
readability and speed of initial development?
one thing i noticed with python type-checking: i found it to be an
absolute nuisance - a hindrance far greater than its value.
the increased function definitions and type definitions frequently
require functions to be expanded from a single horizontal line into a
vertical multi-line definition, running the definition off the page.
the typechecking itself often means that using the Liskov Substitution
Principle is interfered with, because the initial declaration of the
types no longer fit the use to which the over-rides are put.
of course, that *is* the whole point of having the type-checking: to
ensure that the types of base classes and LSP *are* declared!
so i have no clue, here.
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
2020-06-10 12:44 ` Luke Kenneth Casson Leighton [this message]
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=CAPweEDyyM0gyeGj_Aq3_jhokBCQWA_dw7cFaZfNOT-T7Q_J1CQ@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