yui/yui3 — comment on commit 74e2650d8d60fe40ecac83daf83d3e0e3c77127c
File: src/app/js/view.js line 341
By sdesai:

Longer term we may be able to clean it up by:

a) Having the valueFn executed lazily, when the actual call to get/set happens [ maybe some subtle backwards compat issues here (the state of the instance maybe different when the valueFn is called lazily - but maybe something we can try out 3.6.0 PR1 ]

b) Having value of a subclass override valueFn of a superclass. Currently value/valueFn get merged across the hierarchy and then if there are both a valueFn and value at the end of that merge, valueFn takes precedence. The reason for this was that we wanted to come out of the aggregation process with a normalized name:value, instead of holding name:value, and a name:valueFn individually across the hierarchy (everything else gets merged). However we could get a performance improvement by delaying the valueFn call.