Scala path-dependent types: type from reference to member val object seems to be different that type coming directly from original val object?

You would like the compiler to consider lexical. Scanner and mylexical. Scanner as equal, based on the fact that at runtime, the value of mylexical and lexical is always the same.

This is a run-time property, and the type checker doesn't do any data-flow analysis (that would be way too slow to be practical).

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.