News for hackers. Stuff that matters.
Re:Why Julia by ninesigns on Saturday February 23, 2019 @12:34PM (#19234372)
I wish Julia would be more strict wrt type coercion of integer to float values.

I've once spent a day debugging the issue caused by the following line of code, where t1, t2 are floats and v is an array:

d = (t2 - t1) * length(v)

It should've been LinearAlgebra.norm():Float instead of length():Int. Had julia been stricter the code would have failed to run, saving me much time.

Re:Why Julia by tkoolen on Saturday February 23, 2019 @04:37PM (#19235620)
I actually can't think of a single language that doesn't allow you to multiply an integer and a floating point value, yielding a floating point result.
Re:Why Julia by the_duke on Saturday February 23, 2019 @08:54PM (#19236664)
Rust.

In Rust, all type coercion must be explicit, you can't even add different integer types:

5i64 + 5i32 // WONT compile

5i64 + 5i32 as i64 // will work

Re:Why Julia by gmfawcett on Saturday February 23, 2019 @09:02PM (#19236687)
OCaml has distinct multiplication operators for ints and floats. Haskell's multiplication operator requires its arguments to be of the same numeric type, and returns a product of the same type. That's two, off the top of my head...
Re:Why Julia by threatofrain on Sunday February 24, 2019 @03:02AM (#19237646)
JavaScript? 23n + 5 causes a TypeError.
Re:Why Julia by jjtheblunt on Saturday February 23, 2019 @11:14PM (#19237090)
Go ?
Re:Why Julia by ryl00 on Saturday February 23, 2019 @05:44PM (#19235910)
Ada?