Tero Parviainen

Since https://github.com/marcelklehr/vdom-virtualize/ exists, there's little need to duplicate the virtualization code in this project.

Virtual DOM setup code in unit tests could be made less verbose with virtual-doms h-function

Should move away from plain file based dependency management, especially for third-party libs.

We probably can't tap into ngAnimate directly, but similar stuff would be cool.

Would be cool to be able to use the library with forms, with Flux-like architectures. Also look into accessibility and ngAria wrt. forms.

Some sort of eventing system is needed for the library to shine with anything but static views. With events the library would lend itself well to Flux-type architectures and libraries....

A directive for CSS styles, similar to ngStyle, would be useful. I think virtual-dom has some extra support for inline styles, should look into that as well.

A directive for CSS-classes, similar to ngClass, would be useful

Rendering could be made more performant by doing expression parsing and interpolation just once, rather than at each diff. A compile/link distinction analogous with regular directives would probably work well...

The following test fails, because the parent transclusion function is not passed into a nested transclusion as "parentTranscludeFn": ``` it('works with nested transcludes', function() { var injector = makeInjectorWithDirectives({ inner:...