Mark Drobnak

Interesting. I tried this out and LALRPOP seems to accept it. I guess we have to figure out how to do this too. Luckily we can look at LALRPOP's code...

I was just noticing this again today, though mostly when adding a new nonterminal or modifying its grammar. Parsing fails when you have a partial definition (`MyNonterminal: MyTyp^` or `MyNonterminal:...

Yeah, that makes sense because that expansion looks like this (with names): ``` { x: x } // or equivalently just { x } ```

That's an interesting case. I'll think about implementing it. The current architecture doesn't support this because you can only implement Component (effectively) once per type since the interface type is...

I've done some experimentation and this is feasible, but adds some extra verbosity (have to be more explicit about which interface when talking about a component). Have you tried making...

I agree that this is useful, just concerned about ergonomics and introducing more complexity. Here's a possible workaround using the current shaku version that does what you want, though it's...

I have been thinking about extending the derive macro to allow non-trait types (see https://github.com/p0lunin/teloc/issues/8), and it should be pretty easy to allow this. In your example, you need to...

I based the naming of "component" on how [Spring](https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/stereotype/Component.html) and [Autofac](https://autofac.org/) name the "service" classes "components". Dagger's naming in general seems to be a bit different than the rest of...

This is a core issue, because core should make sure web has the necessary privileges and correct environment to run in. I do see that error handling could be improved...

The core issue is that the user wants to use a server which we don't support with a config we didn't create. It's not a situation we can easily detect...