# Redesigning String, optimising small strings and comparison

**URL:** <https://discourse.julialang.org/t/redesigning-string-optimising-small-strings-and-comparison/119716>\
**Category:** Internals & Design\
**Tags:** strings\
**Created:** [September 22, 2024, 6:55pm UTC](https://discourse.julialang.org/t/redesigning-string-optimising-small-strings-and-comparison/119716 "2024-09-22T18:55:36Z")\
**Posts on this page:** 1\
**Showing post:** 58

<div class="post-metadata">

**Author:** ![tecosaur](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tecosaur/32/23206_2.png) [@tecosaur](https://discourse.julialang.org/u/tecosaur)\
**Post date:** [October 1, 2024, 7:44am UTC](https://discourse.julialang.org/t/redesigning-string-optimising-small-strings-and-comparison/119716/58 "2024-10-01T07:44:10Z")

</div>

> [@tecosaur](#):
>
> So, I’m considering making another thread (maybe in #GeneralUsage?), asking for community help putting together a nice collection of string-oriented tasks.

This thread now exists in #General Usage 🙂

> [@Community string benchmark suite](https://discourse.julialang.org/t/community-string-benchmark-suite/120771):
>
> Hello! I’d like your help formulating a high-quality suite of string benchmarks. Over in #Internals & Design I’ve started a conversation about potentially renovating String’s memory representation to reduce memory usage with small strings, and improve comparison performance across the board grinning At this point, a bunch of potential designs have been floated, but one of the things that makes them hard to evaluate is that a lot of the choices come down to tradeoffs, and (just speaking for …

---

_[View the full topic](https://discourse.julialang.org/t/redesigning-string-optimising-small-strings-and-comparison/119716)._