{"shas":[["62b727e976554e5ba81dcc806fa66fabf94ff797","2d55c99f8b037b4a92bd03655e72242678f2a420@5e8d7ff9-d8ef-0310-90f0-a4852d11357a","closes #3977. another case of dealiasing a type, analysing the result, and then using the original one, which could lead to cycles.\nreview by extempore\n(because of recent sin against this holy principle)\n\ngit-svn-id: http://lampsvn.epfl.ch/svn-repos/scala/scala/trunk@24090 5e8d7ff9-d8ef-0310-90f0-a4852d11357a","moors"],["a8382a4d01a764313fa34e62b1a3c2dd84c347a2","2d55c99f8b037b4a92bd03655e72242678f2a420@5e8d7ff9-d8ef-0310-90f0-a4852d11357a","closes #2741, #4079: pickling now ensures that a local type param with a non-local owner, which will thus get a localized owner, will only get a class as its localized owner if its old owner was a class (otherwise, NoSymbol)\nthis ensures that asSeenFrom does not treat typerefs to this symbol differently after pickling.\n\ntodo: should we pro-actively set the owner of these type params to something else than the type alias that they originate from? see notes in typeFunAnon\n\nreview by odersky\n\ngit-svn-id: http://lampsvn.epfl.ch/svn-repos/scala/scala/trunk@24091 5e8d7ff9-d8ef-0310-90f0-a4852d11357a","moors"],["7dd74a350434357d43b2c6a48f79cdd4e98e4076","2d55c99f8b037b4a92bd03655e72242678f2a420@5e8d7ff9-d8ef-0310-90f0-a4852d11357a","    closes #4137. more robust overriding check for type aliases. better error message left as exercise to the reviewer. no review.\n\ngit-svn-id: http://lampsvn.epfl.ch/svn-repos/scala/scala/trunk@24092 5e8d7ff9-d8ef-0310-90f0-a4852d11357a","moors"],["1fb93b1b4e348caa1a76d7c189cff3b909026da5","2d55c99f8b037b4a92bd03655e72242678f2a420@5e8d7ff9-d8ef-0310-90f0-a4852d11357a","closes #3619, #4141. need to exclude implicits from class C in calls to superconstructor from C's constructor.\nreplaced the epic outer.outer.outer by something more robust that goes to the context corresponding to the enclosing class\n\nnextOuter determines which context is searched next for implicits (after `this`, which contributes `newImplicits` below)\nin most cases, it is simply the outer context\nif we're owned by a constructor, the actual current context and the conceptual context are different when it comes to scoping:\nthe current conceptual scope is the context enclosing the blocks that represent the constructor body\n(TODO: why is there more than one such block in the outer chain?)\n\nreview by odersky, extempore\n\ngit-svn-id: http://lampsvn.epfl.ch/svn-repos/scala/scala/trunk@24093 5e8d7ff9-d8ef-0310-90f0-a4852d11357a","moors"]],"repo":"scala/scala","actor":"scala","ref":"refs/heads/master","size":4,"head":"1fb93b1b4e348caa1a76d7c189cff3b909026da5","actor_gravatar":"c0713d6f34649ef9a7358de2ef25379a","push_id":23561802}