# SE-0243: Codepoint and Character Literals

**URL:** <https://forums.swift.org/t/se-0243-codepoint-and-character-literals/21188>\
**Category:** Proposal Reviews\
**Created:** [March 4, 2019, 3:45pm UTC](https://forums.swift.org/t/se-0243-codepoint-and-character-literals/21188 "2019-03-04T15:45:06Z")\
**Posts on this page:** 1\
**Showing post:** 334

<div class="post-metadata">

**Author:** ![xwu](https://avatars.discourse-cdn.com/v4/letter/x/b487fb/32.png) [@xwu](https://forums.swift.org/u/xwu)\
**Post date:** [March 20, 2019, 11:55am UTC](https://forums.swift.org/t/se-0243-codepoint-and-character-literals/21188/334 "2019-03-20T11:55:47Z")

</div>

> [@taylorswift](#):
>
> But, when Swift gets rid of the ICU dependency, this will no longer be true, and `Character` s will be statically verifiable too.

Note that, [as I quoted above](https://forums.swift.org/t/pitch-string-gaps-and-missing-apis/20984/20), grapheme breaking is a runtime concept (intentionally) and not specified by Swift version. It will depend on the version of the stdlib that is linked at run time whether ICU is involved or not, and therefore will not be statically verifiable.

---

_[View the full topic](https://forums.swift.org/t/se-0243-codepoint-and-character-literals/21188)._