News for hackers. Stuff that matters.
Re:A cache miss is not a cache miss by onetimePete on Sunday May 01, 2016 @11:36AM (#11606561)
The real trouble is the inability of chips to identify what haskell could completely avoid, doing the same algorithm for the same input repeatedly. Hashing over input skip and save output, that would be a optimization. Also Tools that give Programmers a DataOrientated-VisualFeedback of the OO-Cluttercosts they impart on there work.

A flag that guarantees side effect freedom to a set of operations and suboperations, for the processor that would be great.

Re:A cache miss is not a cache miss by paulddraper on Sunday May 01, 2016 @01:19PM (#11606966)
Hashing is expensive.
Re:A cache miss is not a cache miss by thrownaway2424 on Sunday May 01, 2016 @07:51PM (#11608404)
Not as expensive as a cache miss.