Jon Pretty

@oferron It's annoying because I don't understand why it makes a difference in this particular case. Usually I can see a reason... :(

@propensive I had a case (might be fixed now) where reordering the implicit params was the key to getting stuff to compile.

@oferron Yeah, implicit parameters work like ordinary parameter *blocks* - evaluated in turn. My problem was with *type* parameters... :(

@oferron It's rare that a different order of implicit parameters will make a difference, but it does sometimes...

@propensive I know implicit are evaluated in blocks, but the order shouldn't matter. Or at least be consistent.

@propensive think about def foo[A, B](l:List[A], f:A=>B) Using this order, A can be inferred, but it won't be. Unless it's higher kinded

@propensive where the order does matter cause it must resolve the constraint. I assume that's what happens in your example (I'm on the phone

@oferron Oh, it's inconsistent... but really useful!