Alexander Lisachenko

> Yeah, this stuff can be dropped. At this point, pointing to roave/better-reflection for most of the "brute-forcing the filesystem, looking for symbols" @Ocramius So, we are going to drop...

@fhein @Ocramius It would be nice to drop all scanners from this library too for 4.0, similarly to annotations, because `roave/better-reflection` or `goaop/parser-reflection` or even `nikic/php-parser` can handle this work...

> Dropping the scanners is probably a better idea for now. Ok, let me check if they could be easily dropped..

> Dropping the scanners is probably a better idea for now. I've checked some dependencies and this is short summary: - Whole `Scanner` namespace could be removed, there are only...

Moved to #155 to separate issue discussion.

Hi, guys! In order to use custom autoloader you should re-init `ReflectionEngine` with composite class locator that will be able to locate your classes or you can use [CallableLocator](https://github.com/goaop/parser-reflection/blob/master/src/Locator/CallableLocator.php) with...

This should be the same: ``` php test::double(Some::class, ['get' => function () { static $index = 0; $mockValues = ['foo', 'bar', 'baz']; return $mockValues[$index++]; }]); ```

Hi, consider to switch to the maintained version of token reflection library: [goaop/parser-reflection](https://github.com/goaop/parser-reflection)

>Only thing which should be extremely useful is to track down dependencies and throw exception when circular dependency is detected. Yes, indeed, this will be nice guard.

Hi, sorry for the delay, wasn't available for OSS. From what I can see, all configuration is correct, will try to reproduce this case locally to see what's wrong with...