Yes, it acts the same as the end anchor which solves most cases but what I've hit are classes leaking out in the other direction.  As an example, with a manifest something like this example I would see failures where `foreman::install` resources would start to be applied before the epel yumrepo was setup.

    class { 'epel': } ->
    class { 'foreman': ... }

You can use stages, resource collector deps, or the anchor pattern to solve this.  I'm surprised a bit suprised an issue like this hasn't come up when using foreman-installer.