|
As of 1.5.1 the issue remains unresolved. This is my patch proposal. This is a pretty major change, and has wide ranging implications – performance, class resolution, etc. While I can see the benefits, we cannot make a change of this scope until we are ready for a major revision (2.0). I'm using the simple non-optional patch by Tomáš Procházka since march 2008 and it works pretty well. As for the "wide ranging implications" I've seen none. Assigning this to Matthew, as he oversees cross-cutting issues like this. I'd like to see a simple one-line comment that says with no uncertainty what we'll be doing- either wait for 2.0 or consider for 1.x. Resolved in trunk and 1.8 release branch |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Resetting priority and assigning for review.