I hope I can use it for control system simulation and deep learning. I want to introduce Julia to my students, but I heard many things about its correctness. I learned Julia but never use it to do any real job. I hope the community has began to solve them. How it is going with the correctness impro…

[image] bertschi: Maybe I just got used to such quirks in dynamic languages, as all of them seem to have issues where silently wrong results can be returned. Here one example from R and Python each, that had bitten me in the past: R: Recycling of vectors with non-matching length That’s an A…

The problem with the topic of Julia and correctness was how it lumped many issues with varying degrees of relevance into One Thing newcomers have to consider. It’s not. Newcomers care about whether they can write practical code that gives the correct results; yes they can, which is why we get more o…

[image] jar1: That’s an API quirk, not a correctness bug – R is designed to do that intentionally. Technically correct, but it has a similar effect to program rather defensively when using it. [image] jar1: The Julia examples like reverse(zip( are incorrect implementations of documented …

If you look at the example in the issue, the mutable functor in question is user-defined: `reverse(Iterators.filter)` can be incorrect if predicate is impure opened 01:17PM - 06 Jul 23 UTC (UTC) closed 07:09PM -…

[image] adienes: I think reverse(::Filter) should be entirely removed :slight_smile: I thought that the thing with composability was that reverse(filter(...)) would work without there being any explicit such method. So either this particular example is not a composability issue, or you can’t…

This is becoming a post on reverse, perhaps this post should be split?

At first wasn’t very concerned about this example. It’s typical of examples meant to illustrate the rampant incorrectness. In general the function is called like map!(c, a, b). In the examples in the doc string, the input and output are clearly not aliased. In fact c is freshly initialized. Many n…

[image] mkitti: My recommendation is for Julia programmers to start conservatively with concrete types such as the one-based Array rather than trying overgeneralize too soon. Using abstract types requires significantly more testing than using concrete types. I have long had a question related…

This is a great list @adienes , thanks. Care to try tackling some of these yourself? Those who notice problems from such issues are usually best-motivated to start fixing them. And thanks for the several pull requests, too!

[image] ufechner7: Thanks for adding it to the 1.10 milestone… It was just removed from the 1.10 milestone (see: sum!, prod!, any!, and all! may silently return incorrect results · Issue #39385 · JuliaLang/julia · GitHub ), which I see as a sign of ignorance of leading team members for correct…

Did Julia community do something to improve its correctness?

General Usage

Topic		Replies	Views
Discussion on "Why I no longer recommend Julia" by Yuri Vishnevsky Community discussion	298	50040	September 9, 2022
Correctness and Multiple Dispatch (Help explain to a julia noob) Community question	13	1163	April 30, 2025
What interface bugs have you ran into in the ecosystem? General Usage question	35	1732	January 31, 2024
At present, in what aspects is Julia still relatively weak compared to other mainstream programming languages? New to Julia question	66	9544	February 5, 2024
Could introducing formal interfaces be nonbreaking? Internals & Design speculative	36	1041	June 4, 2025

Did Julia community do something to improve its correctness?

Related topics