Re:Julia as a unifying end-to-end workflow language on the F...
by jakobnissen on Sunday November 19, 2023 @05:43AM
(#38331354)
What do you mean precisely? Removing @inbounds should never leads to OOB access. The @inbounds macro disables the boundscheck.
If what you mean was that: If the act of removing an @inbounds leads to a bounds exception, then the code was buggy even without the macro. That's true. IIUC, the main issue that Yuri talks about is that Julia is a highly generic language where people share abstractions quite a lot, but there is little agreement on what those abstractions are, and the language provide zero tooling or help with that
[ Parent
| on HN ]
Re:Julia as a unifying end-to-end workflow language on the F...
by phkahler on Monday November 20, 2023 @03:27PM
(#38354169)
>> What do you mean precisely? Removing @inbounds should never leads to OOB access. The @inbounds macro disables the boundscheck.
Oh, that explains it. I thought it enabled a bounds check that somehow allowed code to run rather than fault. So it is a promise to the compiler that the code is correct and doesn't need checking. Composition with arbitrary bounds silently breaks that promise. Go it.