The idea proposed was to have some "common cases" accounted for. Things like `Request` and `Response` are easy to forget if you're building a new controller. There were a few other ideas that would have been far more heavy handed:

1) Build a static class map for all of the Symfony components that might be installed
2) Do some analysis/poll for classes that people frequently forget to `use` and just expand a smaller curated list
3) Dynamically build out a class map at runtime based on the current autoloader rules

I prefer the latter but it would be a lot of work so I started out with a simple map to get the conversation started.