# Weird string slicing in korean

**URL:** <https://discourse.julialang.org/t/weird-string-slicing-in-korean/92252>\
**Category:** Performance\
**Created:** [December 29, 2022, 1:17am UTC](https://discourse.julialang.org/t/weird-string-slicing-in-korean/92252 "2022-12-29T01:17:01Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![stevengj](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevengj/32/71_2.png) [@stevengj](https://discourse.julialang.org/u/stevengj)\
**Post date:** [December 29, 2022, 2:50am UTC](https://discourse.julialang.org/t/weird-string-slicing-in-korean/92252/4 "2022-12-29T02:50:06Z")

</div>

See also this discussion:

> [@Substring function?](https://discourse.julialang.org/t/substring-function/76675/27):
>
> Not efficiently. The basic argument is that a variable-width encoding with non-consecutive codepoint indices is a good tradeoff to make (memory efficiency + speed, at the cost of less-intuitive indexing) because “give me the m-th codepoint” or “or give me the substring from codepoints m to n” is extremely uncommon in (correct) string-handling code, as opposed to “give me the substring at opaque indices I found in a previous search/loop”. That’s why, [in my previous post](https://discourse.julialang.org/t/substring-function/76675/10), I asked you where your…

---

_[View the full topic](https://discourse.julialang.org/t/weird-string-slicing-in-korean/92252)._