[pitch] Add `Span`-providing Properties to Standard Library Types

Something that might be worth mentioning regarding the proposal is around Domain terminology.

The term "Span" has been reserved by the Otel community for quite some time in reference to Open Telemetry Spans of data (see swift-otel here). I imagine introducing this terminology outside of an Otel domain within a core language feature is going to introduce quite a few unwanted namespacing collisions.

Has there been any discussions around this point and if the term "Span" is appropriate?

Yes, we have discussed this. See the first few messages of the review thread, and also the proposal acceptance post. Standard library names never shadow names from packages, so this is not a source stability issue. Span is a strong term of art for the concept of a contiguous memory range (see C++.)

1 Like