First stable version of Weaver 🎉

Foundations rework

• Dependency Graph: The dependency graph representation has been entirely reworked in order to allow for more flexibility at use. Basically, it is now linked using hash keys rather than direct object references.
• Linker/Inspector: Since the dependency graph changed, the linker & Inspector naturally changed as well. Accessing to data through the graph can now throw, giving a more precise error handling. The visitor algorithm for resolving and building remains fairly the same, but now supports new features, which I will describe a bit below.
• Generator: The generator has been entirely rewritten using Meta. It also supports new features which I will describe below.

Optimizations

• Lexer: A cache (LexerCache) has been added in order to avoid SourceKitten to parse the source files every time (~1s for ~30 files). This cache stores one token list per file. A token list is invalidated once its file has changed after it was stored. The format for storing is an optimized JSON where every key is only one or two characters.
• Generator: The generated Swift code is now relying a lot more on runtime, which brings more flexibility for supporting new features, but also allows Weaver to generate one single dependency container per project instead of one per injectable type
• Misc optimizations as a result of profiling the binary (~0.5s instead of ~2s for ~30 files when cache is complete).

New Features

• Property wrapper support. With Swift 5.1, Weaver is now able to detect property wrappers named @Weaver(...) as annotations.
• Dependencies can now be resolved by name and/or by type.
• Abstract types can be composite (eg. A & B) and still be resolved correctly as soon as a registration is declared up the tree with a super set abstract type (eg. A & B & C).
• Some new (more specific) errors are now thrown. Eg. type mismatch, ambiguous type, ambiguous dependency name, etc...
• Added generation of a stub implementation of the main dependency resolver to facilitate testing. The code is generated in a separated file WeaverTests.swift.
• Added scope lazy which activates a lazy loading mechanism for a given dependency.
• Added configuration attribute setter which makes Weaver generate a setter for a given dependency.
• An injectable type can now reference itself. The stored reference is weak, avoiding retain cycles. The optionality of that reference is abstracted away by Weaver though.

Breaking changes

• Only one unique file per target (app/tests) can be generated while Weaver used to offer an option to generate multiple files.
• Naturally, the xcfilelist command has been removed since its necessity was very limited by the fact that only one file is generated now.
• Detailed resolvers are always on, which means the option doesn't exist anymore.
• Custom stencil templates aren't supported anymore, since Stencil has been replaced by Meta.
• The argument --output-path has been renamed to --main-output-path in order to go along with the --test-output-path.