As long as you avoid name collisions with any other implicit on Array (e. G ArrayOps in 2.8, which adds the collections methods), you can extend using the normal implicit pimp-my-library pattern.
As long as you avoid name collisions with any other implicit on Array (e.g. ArrayOps in 2.8, which adds the collections methods), you can extend using the normal implicit pimp-my-library pattern: class FooArrayT(at: ArrayT) { def foo() = at. Length*at. Length } implicit def array2fooT(at: ArrayT) = new FooArray(at) scala> Array(1,2,3).
Foo res2: Int = 9.
Implicit conversions are not prevented by the final-ness of the input class. String, for example, has an implicit conversion to RichString (Scala 2.7) or StringOps (Scala 2.8). So you're free to define implicit conversions for Array with one key caveat: You must forgo Scala's built-in implicit conversion from Array to ArrayOps (in Scala 2.8 only).
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.