Java static keyword bug???
Jump to navigation
Jump to search
Revision as of 30 November 2017 at 15:13.
The highlighted comment was edited in this revision. [diff]
The highlighted comment was edited in this revision. [diff]
I've been experiencing noticeable performance regression after a refactor, which theoretically with the only difference being an static keyword was added to a private final double[] (whose content is never changed).
removing that "static" keyword immediately return my performance back, and adding it back effectively decrease my score, so I'm pretty sure that is the reason. so here is my question, how Java handles static final arrays? may that be some bug introduced by optimizations?
