00:25 <erip> Hey, all. Is it possible to use a generic within a lambda?

00:26 <SeanTAllen> not sure what you mean ericp

00:26 <erip> I have the following: https://gist.github.com/erip/c4810f781606263e0c733cc8e35230fa

00:28 <SeanTAllen> i cant see the error because that doesn't compile, could be kind of hard to debug.

00:28 <erip> I've tried to make it easy mode by including the error in the comment

00:28 <SeanTAllen> where's the lambda?

00:29 <SeanTAllen> o i c it

00:29 <erip> L14

00:29 <SeanTAllen> hmm, its an object literal. i'm not sure. i'm guessing no. i don't use object literals a lot, but i'm the wrong person to ask.

00:29 <SeanTAllen> i'm not going to be able to help.

00:33 <erip> Yeah, this is an interesting problem

00:34 <erip> I don't think the object literal will be constructed until a T is provided -- might be a bug

00:55 <erip> If I replace the T with an A that satisfies the constraints imposed by ponytest's assert_eq, I find something more interesting, but it seems tractable.

07:44 <vaninwagen> erip you cannot have a lambda/object literal with type parameters as those translate to an anonymous class definition and an immediate instantiation where the literal was defined. There is just one instance of that anonymous class, so type params dont make sense here :/

07:45 <vaninwagen> You can thus do sth like:

07:45 <vaninwagen> object is MyInterface[String]

07:45 <vaninwagen> end

07:45 <vaninwagen> ...

08:39 <vaninwagen> But you can have methods with type params on object literals

14:14 <erip> That's too bad about the generic parameter.

15:18 <vaninwagen> Hmmm... Actually looking at your code example, this could work. Maybe you could create an issue. Seems worth a discussion

15:18 <vaninwagen> Merry christmas btw