From: Iruata Souza <iru.muzgo@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] MIPS LSB compiler
Date: Fri, 13 Nov 2009 16:19:20 -0200 [thread overview]
Message-ID: <d1c554290911131019g61ec0db8yf828f84f8cba17f3@mail.gmail.com> (raw)
In-Reply-To: <Pine.BSI.4.64.0911130743300.13404@malasada.lava.net>
On Fri, Nov 13, 2009 at 3:48 PM, Tim Newsham <newsham@lava.net> wrote:
>> * A ducktyping of sorts with interfaces and such. On the surface
>> it just saves
>> you a bunch of "extends XXX", but it actually seems to bridge
>> the gap between
>> dynamically typed world and a statically typed one to an extent
>> that makes me
>> rethink whether static typed languages are as devoid of fun as a
>> Principia Mathematica is.
>
> The type system is more restrictive than duck typing. Thats sort
> of the point of any static type system. But there are useful constructs
> that you can express in a dynamically typed language or a language
> with a more complex type system that you cannot express in go. A
> good, simple example is "map". Go would need generics to support it.
>
$GOOROOT/src/pkg/bytes/bytes.go:248 func ToLower(s []byte) []byte
{ return Map(unicode.ToLower, s) }
next prev parent reply other threads:[~2009-11-13 18:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 4:34 lucio
2009-11-13 5:12 ` Roman Shaposhnik
2009-11-13 6:01 ` John Barham
2009-11-13 17:48 ` Tim Newsham
2009-11-13 18:19 ` Iruata Souza [this message]
2009-11-13 18:36 ` Tim Newsham
2009-11-15 16:52 ` lucio
2009-11-15 17:26 ` Paul Lalonde
2009-11-15 22:25 ` ron minnich
2009-11-15 22:43 ` Bruce Ellis
2009-11-16 4:34 ` lucio
2009-11-16 10:11 ` Bruce Ellis
2009-11-16 4:28 ` lucio
2009-11-13 19:41 ` Andre Guenther
2009-11-15 17:55 ` lucio
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=d1c554290911131019g61ec0db8yf828f84f8cba17f3@mail.gmail.com \
--to=iru.muzgo@gmail.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).