News for hackers. Stuff that matters.

nalimilan

The problem in this case (as with most issues regarding `@inbounds`) is that this text was written before arrays with non-standard indices existed in Julia. So the example was correct at the time it was written, just like the StatsBase code was correct. Old code needs careful checking to fix all these occurrences.
> - DataFrames.jl: Transform does nonsense (use map instead)

What is this supposed to mean?

> - DataFrames.jl: No transpose

This is actually going to be fixed in the next few days (https://github.com/JuliaData/DataFrames.jl/pull/2447). Given the limited amount of work it required, it sounds quite exaggerated to mention it as a major limitation of the language.

Re:Julia v0.7.0 Release Notes on Thursday February 08, 2018 @04:19PM (#16335680)
Existing code won't break as a deprecation is in place. And the replacement is very simple: Matrix(I, m, n), Matrix{Float64}(I, m, n) or even just I depending on the use case.