Serge Shustov

Weird, GitHub shows me that there are no conflicts. Though maybe my merging main into the branch prevents rebase? I guess I could rebase old changes to a new branch...

Disclaimer: I seem to be failing to see the usecase for function injection. It's likely that I'm missing something But in case I'm not missing something there here is my...

Ok, I see. I guess I'll try to look at function references in annotations or something like that to maybe use for linking interfaces or typealiases to a function... >...

Btw typealias CreateFoo = (A) -> Foo @Inject fun CreateFoo(a: A, @Assisted b: B) : Foo This looks like CreateFoo behaves more like something that `@Provides` then something with things...

Ok, so looks like we want to keep this api as is. So here is my proposal how to do it with assisted factory: @Target(CLASS, TYPEALIAS) annotation class InjectFunction( /**...

I wander if it's worth trying to support multiple functions in a single assisted factory... On one hand it looks weird, on the other hand it kinda allows a weird...

Huh. I didn't think of this similarity. With that in mind supporting such 'almost subconponents' seems a slippery slope

@evant looks like it can be closed - warning shows when property is annotated. Pr isn't marked as closing it because it technically doesn't... Maybe I should've just mark it...

@evant are you ok with the idea that Lazy and lambdas would always create new instances (unless things are scoped) instead of reusing existing instances from the existing cycle-breaking mechanism?...