Adding a helper method that reduces a lot of boilerplate of adding spans for user-code to a application, allowing users to quickly wrap existing calls with a span and it looks something like this:

use Sentry\State\Scope;
use Sentry\Tracing\SpanContext;
use function Sentry\Laravel\trace;

$args = [...];

$resutl = trace(
    function (Scope $scope) use ($args) {
        $scope->setTag('some-tag', 'some-value');

        return $this->doSomethingMeasureable($args);
    },
    tap(new SpanContext, function (SpanContext $context) use ($args) {
        $context->setOp('something.measurable');
        $context->setData(['context' => $args]);
        $context->setDescription('Something measurable');
    }),
);

The SpanContext is a unfortunate object in our API at the moment and doesn't have a fluent interface so I've used the tap() helper from Laravel to keep it a little more readable.

In this exampel we also pass the current scope to the callback that is being traced, this might be a good idea or not... maybe the user should wrap this block in their own withScope but it seems easy enough to ignore if you don't want to do anything with the scope.

(this is inspired by a homegrown method I'm using in my applications to make this easier but simplified to make it more general and acceptable)

This is very much a concept and naming might probably change a lot in the process.