On 28 September 2014 20:34, Michał Wadas <michalwadas at gmail.com> wrote:
> We have Object.observe (asynchronous callback whenever object
> properties changes), but do we need Function.observe (asynchronous
> callback whenever function is called)?
>
> Cons:
> - can prevent many optimizations (but Object.observe too)
>
> Pros:
> - allows easy debugging and profiling
> - allows extending libraries functionalities without modyfing their
> code (widgets?)
>
> What should be eventually received by callback code? Possible options:
> - arguments (can prevent certain optimizations; critical for debugging
> and profiling)
> - caller
> - callee
> - function's execution time
> - thisArg of observed function (critical for observing methods of prototype)
Won't happen. This would be a _gigantic_ encapsulation leak, and is
bound to cause security issues without end.
/Andreas
domenic at domenicdenicola.com (2014-10-05T23:40:58.093Z)
Won't happen. This would be a _gigantic_ encapsulation leak, and is
bound to cause security issues without end.
