Would it be possible to solve this without introducing a new route-string-name custom phpdoc type? Ideally, I would like to move away from having to override so many of Laravel's doc types through the use of stubs---they're a pain to maintain (especially when you add all the different version into the mix), they easily become out of sync, and they also have a compound effect where if you override a class you tend to have to add other stubs because you can't reference classes in a stub that are not also stubs.

I've been trying to push a lot of the stubs into the framework, and they've generally been amenable to the changes. One of the things that we can't move to the framework is the model-property type, but I've been thinking of some ideas on how to enable the model property check without having to override all the docs (because there's a ton of them). This would also solve #676 as the stubs would not need to be updated. We could still keep the custom type for users to use in app-land, but we would not have to override all the framework stubs

@calebdw I am just the guy doing copy-paste.

My wish is to detect non-existent route names.