Bug 142172 [Wizards] Small overhead in WizardDialog
Here is code of method WizardDialog.updateDescriptionMessage: private void updateDescriptionMessage() { pageDescription = currentPage.getDescription(); setMessage(currentPage.getDescription()); } As you can see, it access currentPage.getDescription() two times, but value of this method is already in field pageDescription.
bundles/org.eclipse.jface/src/org/eclipse/jface/wizard/WizardDialog.java
* @see #saveUIState
     */
    private void restoreUIState(Map state) {
        restoreEnableState(backButton, state, "back"); 
        restoreEnableState(nextButton, state, "next"); 
        restoreEnableState(finishButton, state, "finish"); 
        restoreEnableState(cancelButton, state, "cancel"); 
        restoreEnableState(helpButton, state, "help"); 
        Object pageValue = state.get("page"); 
        if (pageValue != null) {
			((ControlEnableState) pageValue).restore();
		}
    }
    /**
     * This implementation of IRunnableContext#run(boolean, boolean,
     * IRunnableWithProgress) blocks until the runnable has been run,
     * regardless of the value of <code>fork</code>.
     * It is recommended that <code>fork</code> is set to
     * true in most cases. If <code>fork</code> is set to <code>false</code>,
     * the runnable will run in the UI thread and it is the runnable's
     * responsibility to call <code>Display.readAndDispatch()</code>
     * to ensure UI responsiveness.
     * 
     * UI state is saved prior to executing the long-running operation and is 
     * restored after the long-running operation completes executing.  Any attempt  
     * to change the UI state of the wizard in the long-running operation will be 
     * nullified when original UI state is restored.
     * 
     */
    public void run(boolean fork, boolean cancelable,