See sensiolabs/SensioFrameworkExtraBundle#436 for my plan to remove ParamConverters and replace them with configurable argument resolvers.

Would this also bring support for fooAction(string $foo, Post ...$post)? I'm not sure if isArray() is the correct naming though, what about isCollection() or isTypedArray()? When I think of isArray(), I'd think of array $foo, which can already be deduced from the type.

I love the expansion though, will be a great addition. Regarding the performance for annotation reading, is this going to be cached away? What about the doctrine annotations? As they are a pretty important thing for the ParamConverters.

Do we still need this now that we have seamless service injection?
At least, the second example could be rewritten as:

   /**
     * @Route("/page/{page}", requirements={"page": "[1-9]\d*"}, name="blog_index_paginated")
     */
    public function indexAction(PostRepository $repos, $page)
    {
        $posts = $repos->findLatest($page);
    }

I'd prefer this vs putting code in an annotation. Are there any other cases?

@nicolas-grekas while that example seems very nice, it has 3 drawbacks:

1. I have to manually call the repository and implement what happens if it can't be found in each and every action.
2. I have to add a lot more config, as I rely on the automatic conversion of the parameter converter, which is 0 config in the current state.
3. I can't do @Security("VIEW_PAGE", page)

I'm closing this one as I won't have time to work on it in the coming months. If someone wants to take over, feel free to do so.