From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on ip-172-31-74-118.ec2.internal X-Spam-Level: X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.5-pre1 Path: eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!aioe.org!peer02.ams4!peer.am4.highwinds-media.com!news.highwinds-media.com!newsfeed.neostrada.pl!unt-exc-02.news.neostrada.pl!newsfeed.pionier.net.pl!pwr.wroc.pl!news.wcss.wroc.pl!not-for-mail From: antispam@math.uni.wroc.pl Newsgroups: comp.lang.ada Subject: Re: Multiple dispatch in Julia Date: Sun, 15 Nov 2020 12:43:27 +0000 (UTC) Organization: Politechnika Wroclawska Message-ID: References: <6faed833-462a-4b4b-b555-9a632fd7caddn@googlegroups.com> NNTP-Posting-Host: hera.math.uni.wroc.pl X-Trace: z-news.wcss.wroc.pl 1605444207 20083 156.17.86.1 (15 Nov 2020 12:43:27 GMT) X-Complaints-To: abuse@news.pwr.wroc.pl NNTP-Posting-Date: Sun, 15 Nov 2020 12:43:27 +0000 (UTC) Cancel-Lock: sha1:TrWQKy6cSTgAZlxRIYUoORmle/c= User-Agent: tin/2.4.3-20181224 ("Glen Mhor") (UNIX) (Linux/4.19.0-10-amd64 (x86_64)) X-Received-Bytes: 3126 X-Received-Body-CRC: 2127833215 Xref: reader02.eternal-september.org comp.lang.ada:60585 List-Id: Dmitry A. Kazakov wrote: > On 13/11/2020 13:55, antispam@math.uni.wroc.pl wrote: > > Dmitry A. Kazakov wrote: > >> On 12/11/2020 22:22, antispam@math.uni.wroc.pl wrote: > >>> Dmitry A. Kazakov wrote: > >>>> On 12/11/2020 18:56, antispam@math.uni.wroc.pl wrote: > >>>>> Dmitry A. Kazakov wrote: > >> > >> Either you have static typing or not. But there is no disagreement. You > >> said you do not know how to implement multiple dispatch (while keeping > >> the language statically typed), I said same thing. > > > > I do not see why failure (error) during dispatch would > > conflict with static typing. > > Because it violates typing. A multiple dispatch method is declared as > acting on the whole Cartesian product of classes of arguments and/or the > result. Violating that is type error. In Ada you cannot declare such > methods ARM 3.9.2 (12). OK, Ada defines it own terminology, conflicting with terminology used outside Ada. Since this discussion clearly goes beyond Ada features my assumption was that general terminology applies. Anyway, I think that I know what you are saying. I strongly disagree with several your views, but new arguments are unlikely to appear, so I skip most things. But I can not resit comment about your integer addition example... > > As long as it is detected at runtime > > program will produce correct result or signal error. > > Limited effect of an error does not make it no error. You can implement > addition so that it would sporadically return wrong results. Most languages do so... > If you can > detect that the result is incorrect would such detection magically make > it right? Standard Ada detects overflow instead of returning result. Is Ada wrong? I usualy do integer arithmetic in language where overflow is impossible, but it can run out of memory. It is impossible to do better. Is world fundamentally wrong? -- Waldek Hebisch