Re^4: Thread::Queue memory issue with nested maps but not foreach loops...

It doesn't (I think "can't", but I not sure of that), stop the input list being built.

It could be done. The opcode checker can transform the opcode tree when it detects a pattern that can be optimised. It can even be implemented in a module outside of core.

Comment on Re^4: Thread::Queue memory issue with nested maps but not foreach loops...

Replies are listed 'Best First'.
Re^5: Thread::Queue memory issue with nested maps but not foreach loops... by BrowserUk (Patriarch) on Mar 03, 2012 at 09:41 UTC
If it is possible, I'm really surprised it hasn't been done already. Seems such an obvious thing if there are no technical limitations preventing it. With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. The start of some sanity?	[reply]

Replies are listed 'Best First'.

Re^5: Thread::Queue memory issue with nested maps but not foreach loops...
by BrowserUk (Patriarch) on Mar 03, 2012 at 09:41 UTC

If it is possible, I'm really surprised it hasn't been done already. Seems such an obvious thing if there are no technical limitations preventing it.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

The start of some sanity?

[reply]