# StringIndex idea (Julia 2.0)

**URL:** <https://discourse.julialang.org/t/stringindex-idea-julia-2-0/107185>\
**Category:** Internals & Design\
**Tags:** strings, indexing\
**Created:** [December 5, 2023, 8:23pm UTC](https://discourse.julialang.org/t/stringindex-idea-julia-2-0/107185 "2023-12-05T20:23:43Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![nalimilan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nalimilan/32/147_2.png) [@nalimilan](https://discourse.julialang.org/u/nalimilan)\
**Post date:** [December 5, 2023, 9:26pm UTC](https://discourse.julialang.org/t/stringindex-idea-julia-2-0/107185/11 "2023-12-05T21:26:53Z")

</div>

> [@mbauman](#):
>
> Reminds me of the old [julia#9297](https://github.com/JuliaLang/julia/issues/9297). @nalimilan: was performance the major limiting factor there? Sure seems like we should do much better on that front these days.

AFAICT I abandoned the idea of a `StringIndex` storing a codeunit index plus an offset in chars (as proposed here) for performance reasons (see [this comment](https://github.com/JuliaLang/julia/issues/9297#issuecomment-70404370)). Sorting a pointer was fast but raised problems. But the compiler may have improved since then.

---

_[View the full topic](https://discourse.julialang.org/t/stringindex-idea-julia-2-0/107185)._