Juriy Zaytsev

@rwwagner90 I think being able to jump to the source of a modifier would be helpful. In the case of the css-transitions, I wanted to debug which classes are added/removed...

[Want this as well](https://twitter.com/kangax/status/424653311535755264); chiming in for updates.

### "Not optimized: Inlining bailed out" #### Example ``` js var obj = { prop1: ..., prop2: ... }; function f(obj) { obj.someOtherProp = ...; } f(obj); ``` or: ```...

### What: "Not optimized: ForInStatement is not fast case" #### Example ``` js for (var prop in obj) { /* lots of code */ } ``` #### Possible fix ```...

### "Not optimized: Bad value context for arguments value" #### Example: ? #### Possible fix: ?

(just pasting some notes; perhaps will come in useful)

### "Not optimized: Optimized too many times" #### Example: ? #### Possible fix: ? [kOptimizedTooManyTimes](https://code.google.com/p/v8/codesearch#v8/trunk/src/compiler.cc&q=kOptimizedTooManyTimes&sq=package:v8&type=cs&l=320)

@acthp you're right, I made a mistake in my example (mind you, this is simply my assumption about the error — I haven't worked on a profiler, I don't know...

I ran into the same issue with custom components in our codebase. This rule is reporting false positives (more like: positives or negatives depending on if custom component adds role="presentation"...

@Kovensky is there some kind of reference to find out more about this — why is it no longer relevant? what exactly was changed and how? etc.