Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!zen.net.uk!dedekind.zen.co.uk!reader02.nrc01.news.zen.net.uk.POSTED!not-for-mail
From: Nobody <nobody@nowhere.com>
Subject: Re: A Pragmatic Case for Static Typing
Date: Tue, 03 Sep 2013 02:10:37 +0100
User-Agent: Pan/0.14.2 (This is not a psychotic episode. It's a cleansing moment of clarity.)
Message-Id: <pan.2013.09.03.01.10.36.789000@nowhere.com>
Newsgroups: comp.lang.python
References: <8bc2f539-ae7a-4cd8-83c0-91449aecd616@googlegroups.com> <7xfvtnwsn9.fsf@ruckus.brouhaha.com> <52245df4$0$2743$c3e8da3$76491128@news.astraweb.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Lines: 10
Organization: Zen Internet
NNTP-Posting-Host: 6b41b48b.news.zen.co.uk
X-Trace: DXC=9AHhcF08P0a4cU[DET<O[k]G;bfYi23hd=dR0\ckLKG`WeZ<[7LZNRf5:9_Qi7c;5lM2Z^cWRFGAkehXR3`1aCSg
X-Complaints-To: abuse@zen.co.uk
Xref: csiph.com comp.lang.python:53547

On Mon, 02 Sep 2013 09:44:20 +0000, Steven D'Aprano wrote:

> One factor I don't see very often mentioned is that static typing 
> increases coupling between distant parts of your code. If func() changes 
> from returning int to MyInt, everything that calls func now needs to be 
> modified to accept MyInt, no matter how similar MyInt is to int. You have 
> to make changes just to satisfy the compiler.

Not if the language has type inference (e.g. Haskell, or C++ templates).