What was the reason to restrict on combining implicit parameters and view/context bounds?

Context and view bounds add implicit parameters. So if you write: def fT : Manifest(l: ListT)(implicit ord: OrderingT) There are, in fact two implicit parameters being passed instead of one. Allowing this kind of syntax will certainly result in some confusion down the road.As implicit parameter usage starts to get more widespread, because of type classes, being able to do something like the above is helpful.

Context and view bounds add implicit parameters. So if you write: def fT : Manifest(l: ListT)(implicit ord: OrderingT) There are, in fact, two implicit parameters being passed instead of one. Allowing this kind of syntax will certainly result in some confusion down the road.As implicit parameter usage starts to get more widespread, because of type classes, being able to do something like the above is helpful.

Context and view bounds add implicit parameters" >> sure, I know that. I was rather interested, if it's caused with any technical difficulty. – Vasil Remeniuk Jul 27 at 5:19 IMO, not being able to use the bounds along with implicit parameters might also be very confusing for a newbie :) – Vasil Remeniuk Jul 27 at 5:22 @Vasil I'm not saying it is a bad decision, just that it adds a certain degree of... confusion.It would be illegal to call the above function like f(List(1 -> 2, 2 -> 1))(Ordering by (_.

Swap)), even though it seems to have all parameter lists filled correctly. – Daniel C. Sobral Jul 27 at 15:18 very true, I agree – Vasil Remeniuk Jul 27 at 15:23.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.