News for hackers. Stuff that matters.
Re:The type system is a programmer's best friend by throwawaymaths on Saturday November 05, 2022 @10:33AM (#33481844)
It's also something that some languages seriously screw up. Consider multiplying a time (which is typed in go) with a numerical value... suppose what I want is a user to input number of time intervals to wait. So the user wants 5, and the interval is 2500 milliseconds. The way you get 12500 milliseconds out of that made me want to throw my computer out the window.
Re:The type system is a programmer's best friend by Chinjut on Saturday November 05, 2022 @12:42PM (#33483096)
I don't understand. What should you get instead?
Re:The type system is a programmer's best friend by morelisp on Saturday November 05, 2022 @04:30PM (#33485331)
Go does not have operator overloading, and numeric operators must have identical types. So if you have `var x int = 5` and `var t time.Duration = 2500 * time.Millisecond`, you have to `time.Duration(5) * t` or `time.Duration(x * int(t))`.

It's slightly better than languages with no operator overloading nor newtypes at all (well, actually a lot better given other things you can use newtypes for) but without operator overloading using it just for units, with no other API machinery, is usually a bad idea.

Re:The type system is a programmer's best friend by throwawaymaths on Monday November 07, 2022 @11:28AM (#33507982)
Two options:

1. Don't type units like that.

2. Allow the * operator to multiply a time-unitful value with an untimed scalar and disallow using it with two time-unitful values.

Presumably the requirement that * operands are the same is arbitrarily modifiable and go developers have control over what types operators take.

Re:The type system is a programmer's best friend by morelisp on Monday November 07, 2022 @01:44PM (#33510244)
1. Uh, ok. Might as well throw out the whole thread then?

2. A "time unit" is not a special type of value. You can construct arbitrary types of integers, and it is common to do so. `*` has no clue what a time is, just that it's "not an int" (for example).

Re:The type system is a programmer's best friend by xigoi on Saturday November 05, 2022 @05:16PM (#33485869)
The commenter you're replying to expressed it confusingly. The point is that in Go, 5 * time.Milliseconds(2500) is a type error, and instead you need to do time.Nanoseconds(5) * time.Milliseconds(2500).
Re:The type system is a programmer's best friend by morelisp on Saturday November 05, 2022 @05:39PM (#33486109)
`5 * time.Milliseconds(2500)` is not a type error, though `int(5) * time.Milliseconds(2500)` is.

(This is especially relevant because you really mean `5 * (2500 * time.Millisecond)` vs. int(5) * (2500 * time.Millisecond)`, as there is no `time.Milliseconds` function.)

Re:The type system is a programmer's best friend by xigoi on Saturday November 05, 2022 @05:58PM (#33486299)
Thanks, I don't remember exactly how it worked. It doesn't take away from the stupidity.