Re:Fortran is still a thing
by johncolanduoni on Tuesday November 27, 2018 @02:00PM
(#18545469)
That was due to a bug in LLVM when noalias was used in conjunction with LLVM’s stack unwinding facilities. It’s since been re-enabled now that the upstream bug has been fixed: https://github.com/rust-lang/rust/pull/50744
> It’s since been re-enabled
It's since been disabled again, due to a new bug (which was also reproduced in C, on both LLVM and GCC): https://github.com/rust-lang/rust/issues/54878
Re:Fortran is still a thing
by steveklabnik on Tuesday November 27, 2018 @02:37PM
(#18545908)
> most numerical computing friendly features in Rust tend to be on the back burner
Yes and no, we’ve been working on underlying stuff that will be needed in order to ship those features, and while a roadmap for next year has not been decided, most believe it will be a major component.
Re:Fortran is still a thing
by ballenarosada on Tuesday November 27, 2018 @08:14PM
(#18548437)
Anything in particular you would highlight? I've been following const generics development, but other than that I'm not too clued in. Thanks!
Re:Fortran is still a thing
by steveklabnik on Wednesday November 28, 2018 @12:27AM
(#18549491)
We accepted an RFC for integer generics, but it needed same the underlying work that const generics needed.
There is no aliasing in Fortran. In C (and using compiler extensions in C++) you manually use restrict to give the same information to the compiler, but it is a trickier process than in Fortran. Rust inherits this benefit from Fortran, but last I checked they had all related optimizations disabled (and most numerical computing friendly features in Rust tend to be on the back burner).