Type Systems Explained with Examples • Hacker News Board

Re: Type Systems Explained with Examples

#11

Post by keybuk » Tue, Sep 29, 2020, 5:16 AM UTC

nvader wrote: post #4

I would pay good money for a comparison of type systems, delivered in the vein of Cow Economics. In Self, you have a cow. You ask the cow to moo. It moos. In Java, you have a cow. You construct a CowMooFactory to create an MooIpml. The MooImpl moos. In Python, you have a cow. You ask it to moo. It quacks. In C, you have a pointer to a cow. You ask it to moo. Segmentation fault (core dumped).

In Swift, if cow is a reference type you all share a cow that moos whoever asks, but if cow is a value type then you all have your own copy of a cow that only moos for you.

Re: Type Systems Explained with Examples

#12

Post by dcre » Tue, Sep 29, 2020, 5:47 AM UTC

I suspect the use of “semantic” where it should be “semantics” is explained by the French author translating “semantique” a little too directly.

Re: Type Systems Explained with Examples

#13

Post by leloctai » Tue, Sep 29, 2020, 5:59 AM UTC

samatman wrote: post #6

nvader wrote: post #4

I would pay good money for a comparison of type systems, delivered in the vein of Cow Economics. In Self, you have a cow. You ask the cow to moo. It moos. In Java, you have a cow. You construct a CowMooFactory to create an MooIpml. The MooImpl moos. In Python, you have a cow. You ask it to moo. It quacks. In C, you have a pointer to a cow. You ask it to moo. Segmentation fault (core dumped).

In ML, your value moos. It is inferred to be a cow. In Ruby, your value moos. Could be a cow; might be a MooDuck. Do you really care?

So what's the difference between ruby and python?

Re: Type Systems Explained with Examples

#14

Post by ClikeX » Tue, Sep 29, 2020, 6:32 AM UTC

leloctai wrote: post #13

samatman wrote: post #6

Earlier quoted context omitted.

In ML, your value moos. It is inferred to be a cow. In Ruby, your value moos. Could be a cow; might be a MooDuck. Do you really care?

So what's the difference between ruby and python?

During the Ruby's runtime the cow might get monkeypatched into a bat.

Re: Type Systems Explained with Examples

#15

Post by tgv » Tue, Sep 29, 2020, 7:08 AM UTC

nvader wrote: post #4

I would pay good money for a comparison of type systems, delivered in the vein of Cow Economics. In Self, you have a cow. You ask the cow to moo. It moos. In Java, you have a cow. You construct a CowMooFactory to create an MooIpml. The MooImpl moos. In Python, you have a cow. You ask it to moo. It quacks. In C, you have a pointer to a cow. You ask it to moo. Segmentation fault (core dumped).

That doesn't make any sense.

Re: Type Systems Explained with Examples

#16

Post by Konohamaru » Tue, Sep 29, 2020, 8:23 AM UTC

> or to perform “impossible” operations, like division by 1.

This looks like a mistake.

Re: Type Systems Explained with Examples

#17

Post by ealhad » Tue, Sep 29, 2020, 8:49 AM UTC

nvader wrote: post #4

I would pay good money for a comparison of type systems, delivered in the vein of Cow Economics. In Self, you have a cow. You ask the cow to moo. It moos. In Java, you have a cow. You construct a CowMooFactory to create an MooIpml. The MooImpl moos. In Python, you have a cow. You ask it to moo. It quacks. In C, you have a pointer to a cow. You ask it to moo. Segmentation fault (core dumped).

In Rust, you have a Cow. It's smart and allows you to clone borrowed things, including things which can moo.

Re: Type Systems Explained with Examples

#18

Post by tomp » Tue, Sep 29, 2020, 10:11 AM UTC

leloctai wrote: post #13

samatman wrote: post #6

Earlier quoted context omitted.

In ML, your value moos. It is inferred to be a cow. In Ruby, your value moos. Could be a cow; might be a MooDuck. Do you really care?

So what's the difference between ruby and python?

In Ruby, the cow moos automatically.

Re: Type Systems Explained with Examples

#19

Post by Joker_vD » Tue, Sep 29, 2020, 10:36 AM UTC

ealhad wrote: post #17

nvader wrote: post #4

I would pay good money for a comparison of type systems, delivered in the vein of Cow Economics. In Self, you have a cow. You ask the cow to moo. It moos. In Java, you have a cow. You construct a CowMooFactory to create an MooIpml. The MooImpl moos. In Python, you have a cow. You ask it to moo. It quacks. In C, you have a pointer to a cow. You ask it to moo. Segmentation fault (core dumped).

In Rust, you have a Cow. It's smart and allows you to clone borrowed things, including things which can moo.

But only clones on write, which is a useful optimization.

Re: Type Systems Explained with Examples

#20

Post by Joker_vD » Tue, Sep 29, 2020, 10:40 AM UTC

dcre wrote: post #12

I suspect the use of “semantic” where it should be “semantics” is explained by the French author translating “semantique” a little too directly.

Why does English has all those random "s" at the end of the Greek-borrowed words? AFAIK, most other languages that borrowed the same words don't have those.