# \[Pitch #2\] Regex Literals

**URL:** <https://forums.swift.org/t/pitch-2-regex-literals/56736>\
**Category:** Pitches\
**Created:** [April 13, 2022, 5:56pm UTC](https://forums.swift.org/t/pitch-2-regex-literals/56736 "2022-04-13T17:56:28Z")\
**Posts on this page:** 1\
**Showing post:** 46

<div class="post-metadata">

**Author:** ![stackotter](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/stackotter/32/20670_2.png) [@stackotter](https://forums.swift.org/u/stackotter)\
**Post date:** [April 15, 2022, 9:23pm UTC](https://forums.swift.org/t/pitch-2-regex-literals/56736/46 "2022-04-15T21:23:36Z")

</div>

> [@Francois\_Green](#):
>
> If you beat the Swift team to a symbol, do you own it? Maybe there should be a broader discussion about this.

They don't "own it", but the point is that it would be a pretty big source breaking change that should really be avoided unless completely necessary. Even if those libraries didn't exist, it would still be a source breaking change.

I will point out that these aren't the only examples of libraries that break due to the `/.../` syntax. As @mishal_shah pointed out, this syntax breaks 16 projects out of the 2968 in the Swift Package Index. That certainly isn't insignificant. I believe that following the precedent set by other languages is no reason to introduce source breaking changes, especially since two popular packages would get broken along with all their clients.

> [@mishal\_shah](#):
>
> - Total packages - 2968
> - 16 Projects failed due to Regex Literal change
> - 15 Projects failed with `error: prefix operator may not contain '/'`
> - 1 Project failed due to `/` ambiguity
> 
> - 74 Projects failed due to unrelated reasons

---

_[View the full topic](https://forums.swift.org/t/pitch-2-regex-literals/56736)._
