First of all I wouldn't say that there is any striking consistency in the FastTrack code. There is both implicit conversion-based code and non-implicit based (e.g. currentMirror). There is code that uses info directly from the context and there is info that partially extracts trees right in the fast track. 

Second of all, I would argue that implicit conversions there are a complete overkill that makes code harder to read and are an example of casual usage of a feature that is generally frowned upon to save a few keystrokes. 

Lastly, considering the fact that all the macros that are expanded through FastTrack are basically the same from expansion point of view I wonder why isn't there some common interface/trait to make all of them truly consistent and uniform:

```
trait FastTrackMacro {
   val c: Context
   def expand: Tree 
}
```