@pcwalton Odd that there's no warning for using "move" on a stack vector that's doomed to be copied.
-
-
-
@jruderman Generally we drew the line at warnings for copies at "requires a malloc", but that could be tweaked perhaps with lint options.
End of conversation
New conversation -
-
-
@pcwalton I see no 'unsafe' in the benchmark but looks like there is in the floor() fn. -
@robknight_ It's part of the standard library that calls an LLVM intrinsic. I was considering that part of the runtime.
End of conversation
New conversation -
-
-
@pcwalton You can avoid copying arrays, making the benchmark's first phase 15% faster: https://gist.github.com/4499079Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@pcwalton It's 50% slower when the "pixels" array is two-dimensional. Why? I thought that would help w bounds checks. https://gist.github.com/4499157Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@pcwalton can we get a StrategoXT-like pattern matching in rust please? ^^Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.