“No options” simply isn’t true. Here’s a guide to many of the options: <a href="https://hasufell.github.io/posts/2024-05-07-ultimate-string-guide.html" rel="nofollow">https://hasufell.github.io/posts/2024-05-07-ultimate-string-...
Now if you’re asking why the basic prelude String type remains as it is, that’s because changing it would break more code than it’s worth, at least as far as prelude’s maintainers are concerned. This is no different from how standard C strings remain a null-terminated sequence of bytes even though that’s been awful for everyday use for at least 30 years.
Note that using linked lists for strings is actually more "parallel friendly" because you can take the head/tail and spread it around 16k GPU cores in O(1), unlike in Haskell, unlike arrays, which require a linear copy, becoming quadratic. So, the right "default type" isn't that clear on Bend, because GPUs behave very differently from CPUs.
That said, yes, we definitely should have a compact Text type. I'll add it over the weekend.
wg0 · · focus · HN ↗
> - The compiler (not kernel) is 99% AI-written and has not been fully audited yet.
> - Strings are linked lists of characters, so text processing is slow.
[0]. <a href="https://github.com/bendlang/bend/tree/main" rel="nofollow">https://github.com/bendlang/bend/tree/main
LightMachine · · focus · HN ↗
We will introducing binary buffers eventually. The project is new...
bunderbunder · · focus · HN ↗
Now if you’re asking why the basic prelude String type remains as it is, that’s because changing it would break more code than it’s worth, at least as far as prelude’s maintainers are concerned. This is no different from how standard C strings remain a null-terminated sequence of bytes even though that’s been awful for everyday use for at least 30 years.
LightMachine · · focus · HN ↗
That said, yes, we definitely should have a compact Text type. I'll add it over the weekend.
imtringued · · focus · HN ↗
You can slice up arrays in O(1).
The default type is incredibly clear to me.