This doesn't seem right. Won't this be confusing for people by hiding the scoping information? It looks like foo is defined in f1 instead of showing it under

f1
+--f2
   +--foo
       +--func

The outline view is just designed to have nodes for the {} ranges, i.e. for navigation, i.e. to match the "physical" outline regions that exist in the document -- the full scope on the right is not a priority for the outline view. They would see that either via clicking the item or viewing the right-side if it's visible or doing a Go to Declaration to view the type declaration where the hierarchical scopes exist in the Outline view.

i.e. the reason it should be moved to the right is that it's lower priority info, given the limited UI space of the VS Code UI design. Any confusion about scopes that are hidden on the right don't really matter as much, since it'd be handled by IntelliSense completion or error reporting etc..

I might re-open #8100 for the more difficult solution of creating a node for the "ghost" scopes, i.e. this fix prioritizes making the function name visible on the left when the scope is too big.