Mark Thomas
Mark Thomas
> Should we really support ${'5' + '3'} = 8 in future? Maybe we can deprecate + add config Yes, we should continue to support that. Not doing so means...
You are going to need to provide a test case that demonstrates a memory leak. And once we have such a test case the fix will likely be to address...
I'm still not seeing the evidence of a memory leak. Soft references are GC eligible. For a memory leak I'd expect to see a chain of hard references from the...
There is no memory leak here (confirmed with a profiler). There is nothing to fix. Absent a test case demonstrating an actual memory leak, this PR and the associated issue...
I would very much prefer a test case that demonstrates a leak - a leak being a hard reference to an object that isn't eligible for GC that should be...
>Why do you think this will be garbage collected? Because I have read the code - particularly the `cleanup()` method and when it is called - and tested that it...
This PR really needs to be closed and this discussion moved to the issue. It does seem unlikely to me that there would be enough bean usage to cause notable...
Replaced by #248
PR rebased and Javadoc for `sendEarlyHints()` updated to reflect Greg's review comments.
That looks like a reasonable interpretation of the current Javadoc. Fixing that would be an implementation issue rather than an EL API issue. I think this is something we could...