Dependency injection based programming language

With luck-based typing

Did You ever happen to use a dependency injection pattern?

Dependency injection is a software design pattern that allows the removal of hard-coded dependencies and makes it possible to change them, whether at run-time or compile-time.

What it usually is — a container that will manage your classes, and create them for you. Even if your class has a dependency (reference), that is known to container — it can cope with it. Example:

— Conatiner, please save class FileReader, as IReader. It can read files.
— Container, please save class MailSender, as ISender. It can send emails. It uses IReader to read email contents.

— Container, please give me some ISender, I want to send something.
— There’s Your ISender. By the way, it is a MailSender, with FileReader bundled somewhere inside.

When a program uses DI, its “new” keyword counter decreases a lot. But what would happen, if someone replaced creating new objects with asking them from DI container, by simply calling “new”?

And the DI container, would also take into consideration class name, method names, and parameter types?

What if that container had a distributed index of all published classes, where he could choose from to download?

The code itself provides much information about types it uses. Is it possible to guess some?