Although currently I believe every implementation always provides a span, @michaelficarra has raised the concern that builtins may want the option in the future to omit position information, particularly as it relates to implementation hiding.
It seems reasonable to make the span optional in preparation for this, so that users working with the stack frame structure won't rely on its presence.
Although currently I believe every implementation always provides a span, @michaelficarra has raised the concern that builtins may want the option in the future to omit position information, particularly as it relates to implementation hiding.
It seems reasonable to make the span optional in preparation for this, so that users working with the stack frame structure won't rely on its presence.