just trying to improve complex scenario performance
couple of little optimisations to the expression compiler
getting there with this rewriter
performance back to the fastest, conditional expressions being rewritten correctly and combined rezolvers seem to work correctly.
child containers - benchmark on IOCPerformance is very good if you register the container once and then create lifetimes from it.  In fact, it's ridiculously fast...
should now be able to mix in rezolve calls with expression targets.  Probably needs more work - but there's a test in the shared compiler tests which does it - by taking the result of a rezolve call and passing it to a static method to be used as the constructor parameter.  Nice.
property injection now possible through use of generic expressions and the irezolvetargetadapter.  Only thing is how to support it via non-expression sources!
auto-discovered properties.  Am wondering whether I should also have auto-built targets from parameter and property types.  In theory, the root of a dependency should be an object that either takes simple objects or none at all.
working on open generics at the moment.
many more generic scenarios tested - now have a failing test for resolving a generic via one of its generic interfaces.  That's shere I'm at now.
Working on getting generic type parameters for a target from nested generics passed as type parameters to its base interface.  Got a test which gets the right value - need to plug it back into GenericConstructorTarget.
rezolve open generic where type parameter is identified from a nested generic is done.  Possibly some more scenarios need testing, but it should all work fine.
I think resolving by bases and bases of bases is working
Rudimentary multiple service registration done.  Well, I say rudimentary - it is exactly what is required by most consumers of IOC containers, so it should do just fine.
nearly there with commonservicelocator - just need the package done and published
just adding mvc project into repo so I can sync
doesn't build - need to consider how named rezolvers with sibling registrations under naming paths will work.
before merging to dev
namingis next.