2020-01-18 08:38:21 +00:00
|
|
|
/*
|
2021-11-15 23:47:54 +00:00
|
|
|
* Copyright (c) 2018-2021, Andreas Kling <kling@serenityos.org>
|
2020-01-18 08:38:21 +00:00
|
|
|
*
|
2021-04-22 08:24:48 +00:00
|
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
2020-01-18 08:38:21 +00:00
|
|
|
*/
|
|
|
|
|
2018-10-10 09:53:07 +00:00
|
|
|
#pragma once
|
|
|
|
|
2020-02-14 20:41:10 +00:00
|
|
|
#include <AK/ByteBuffer.h>
|
2020-09-23 11:21:18 +00:00
|
|
|
#include <AK/Format.h>
|
2020-02-14 20:41:10 +00:00
|
|
|
#include <AK/Forward.h>
|
2020-09-22 11:11:05 +00:00
|
|
|
#include <AK/StringView.h>
|
2019-06-14 04:43:56 +00:00
|
|
|
#include <stdarg.h>
|
2018-10-10 09:53:07 +00:00
|
|
|
|
|
|
|
namespace AK {
|
|
|
|
|
|
|
|
class StringBuilder {
|
|
|
|
public:
|
2022-12-04 18:02:33 +00:00
|
|
|
using OutputType = DeprecatedString;
|
2019-08-07 19:28:07 +00:00
|
|
|
|
2022-12-09 16:45:35 +00:00
|
|
|
static ErrorOr<StringBuilder> create(size_t initial_capacity = inline_capacity);
|
|
|
|
|
2020-11-24 21:04:22 +00:00
|
|
|
explicit StringBuilder(size_t initial_capacity = inline_capacity);
|
2021-01-10 23:29:28 +00:00
|
|
|
~StringBuilder() = default;
|
2018-10-10 09:53:07 +00:00
|
|
|
|
2021-11-15 23:47:54 +00:00
|
|
|
ErrorOr<void> try_append(StringView);
|
2022-02-15 22:23:34 +00:00
|
|
|
#ifndef KERNEL
|
2021-11-15 23:47:54 +00:00
|
|
|
ErrorOr<void> try_append(Utf16View const&);
|
2022-02-15 22:23:34 +00:00
|
|
|
#endif
|
2021-11-15 23:47:54 +00:00
|
|
|
ErrorOr<void> try_append(Utf32View const&);
|
|
|
|
ErrorOr<void> try_append_code_point(u32);
|
|
|
|
ErrorOr<void> try_append(char);
|
|
|
|
template<typename... Parameters>
|
|
|
|
ErrorOr<void> try_appendff(CheckedFormatString<Parameters...>&& fmtstr, Parameters const&... parameters)
|
|
|
|
{
|
|
|
|
VariadicFormatParams variadic_format_params { parameters... };
|
|
|
|
return vformat(*this, fmtstr.view(), variadic_format_params);
|
|
|
|
}
|
|
|
|
ErrorOr<void> try_append(char const*, size_t);
|
2022-01-04 22:37:15 +00:00
|
|
|
ErrorOr<void> try_append_repeated(char, size_t);
|
2022-02-24 17:15:31 +00:00
|
|
|
ErrorOr<void> try_append_escaped_for_json(StringView);
|
2021-11-15 23:47:54 +00:00
|
|
|
|
2021-11-10 23:55:02 +00:00
|
|
|
void append(StringView);
|
2022-02-15 22:23:34 +00:00
|
|
|
#ifndef KERNEL
|
2021-08-09 15:53:28 +00:00
|
|
|
void append(Utf16View const&);
|
2022-02-15 22:23:34 +00:00
|
|
|
#endif
|
2021-08-09 15:48:50 +00:00
|
|
|
void append(Utf32View const&);
|
2018-10-10 09:53:07 +00:00
|
|
|
void append(char);
|
2020-08-05 20:31:20 +00:00
|
|
|
void append_code_point(u32);
|
2021-08-09 15:48:50 +00:00
|
|
|
void append(char const*, size_t);
|
|
|
|
void appendvf(char const*, va_list);
|
2022-01-04 22:37:15 +00:00
|
|
|
void append_repeated(char, size_t);
|
2018-10-10 09:53:07 +00:00
|
|
|
|
2021-05-11 13:48:37 +00:00
|
|
|
void append_as_lowercase(char);
|
2021-11-10 23:55:02 +00:00
|
|
|
void append_escaped_for_json(StringView);
|
2020-11-02 11:56:36 +00:00
|
|
|
|
2020-09-22 11:11:05 +00:00
|
|
|
template<typename... Parameters>
|
2021-08-09 15:48:50 +00:00
|
|
|
void appendff(CheckedFormatString<Parameters...>&& fmtstr, Parameters const&... parameters)
|
2020-09-23 11:21:18 +00:00
|
|
|
{
|
2021-08-30 09:58:22 +00:00
|
|
|
VariadicFormatParams variadic_format_params { parameters... };
|
2021-11-16 00:15:21 +00:00
|
|
|
MUST(vformat(*this, fmtstr.view(), variadic_format_params));
|
2020-09-23 11:21:18 +00:00
|
|
|
}
|
2020-09-22 11:11:05 +00:00
|
|
|
|
2022-02-15 22:23:34 +00:00
|
|
|
#ifndef KERNEL
|
2022-12-04 18:02:33 +00:00
|
|
|
[[nodiscard]] DeprecatedString build() const;
|
2022-12-06 01:12:49 +00:00
|
|
|
[[nodiscard]] DeprecatedString to_deprecated_string() const;
|
AK: Introduce the new String, replacement for DeprecatedString
DeprecatedString (formerly String) has been with us since the start,
and it has served us well. However, it has a number of shortcomings
that I'd like to address.
Some of these issues are hard if not impossible to solve incrementally
inside of DeprecatedString, so instead of doing that, let's build a new
String class and then incrementally move over to it instead.
Problems in DeprecatedString:
- It assumes string allocation never fails. This makes it impossible
to use in allocation-sensitive contexts, and is the reason we had to
ban DeprecatedString from the kernel entirely.
- The awkward null state. DeprecatedString can be null. It's different
from the empty state, although null strings are considered empty.
All code is immediately nicer when using Optional<DeprecatedString>
but DeprecatedString came before Optional, which is how we ended up
like this.
- The encoding of the underlying data is ambiguous. For the most part,
we use it as if it's always UTF-8, but there have been cases where
we pass around strings in other encodings (e.g ISO8859-1)
- operator[] and length() are used to iterate over DeprecatedString one
byte at a time. This is done all over the codebase, and will *not*
give the right results unless the string is all ASCII.
How we solve these issues in the new String:
- Functions that may allocate now return ErrorOr<String> so that ENOMEM
errors can be passed to the caller.
- String has no null state. Use Optional<String> when needed.
- String is always UTF-8. This is validated when constructing a String.
We may need to add a bypass for this in the future, for cases where
you have a known-good string, but for now: validate all the things!
- There is no operator[] or length(). You can get the underlying data
with bytes(), but for iterating over code points, you should be using
an UTF-8 iterator.
Furthermore, it has two nifty new features:
- String implements a small string optimization (SSO) for strings that
can fit entirely within a pointer. This means up to 3 bytes on 32-bit
platforms, and 7 bytes on 64-bit platforms. Such small strings will
not be heap-allocated.
- String can create substrings without making a deep copy of the
substring. Instead, the superstring gets +1 refcount from the
substring, and it acts like a view into the superstring. To make
substrings like this, use the substring_with_shared_superstring() API.
One caveat:
- String does not guarantee that the underlying data is null-terminated
like DeprecatedString does today. While this was nifty in a handful of
places where we were calling C functions, it did stand in the way of
shared-superstring substrings.
2022-12-01 12:27:43 +00:00
|
|
|
ErrorOr<String> to_string() const;
|
2022-02-15 22:23:34 +00:00
|
|
|
#endif
|
AK: Introduce the new String, replacement for DeprecatedString
DeprecatedString (formerly String) has been with us since the start,
and it has served us well. However, it has a number of shortcomings
that I'd like to address.
Some of these issues are hard if not impossible to solve incrementally
inside of DeprecatedString, so instead of doing that, let's build a new
String class and then incrementally move over to it instead.
Problems in DeprecatedString:
- It assumes string allocation never fails. This makes it impossible
to use in allocation-sensitive contexts, and is the reason we had to
ban DeprecatedString from the kernel entirely.
- The awkward null state. DeprecatedString can be null. It's different
from the empty state, although null strings are considered empty.
All code is immediately nicer when using Optional<DeprecatedString>
but DeprecatedString came before Optional, which is how we ended up
like this.
- The encoding of the underlying data is ambiguous. For the most part,
we use it as if it's always UTF-8, but there have been cases where
we pass around strings in other encodings (e.g ISO8859-1)
- operator[] and length() are used to iterate over DeprecatedString one
byte at a time. This is done all over the codebase, and will *not*
give the right results unless the string is all ASCII.
How we solve these issues in the new String:
- Functions that may allocate now return ErrorOr<String> so that ENOMEM
errors can be passed to the caller.
- String has no null state. Use Optional<String> when needed.
- String is always UTF-8. This is validated when constructing a String.
We may need to add a bypass for this in the future, for cases where
you have a known-good string, but for now: validate all the things!
- There is no operator[] or length(). You can get the underlying data
with bytes(), but for iterating over code points, you should be using
an UTF-8 iterator.
Furthermore, it has two nifty new features:
- String implements a small string optimization (SSO) for strings that
can fit entirely within a pointer. This means up to 3 bytes on 32-bit
platforms, and 7 bytes on 64-bit platforms. Such small strings will
not be heap-allocated.
- String can create substrings without making a deep copy of the
substring. Instead, the superstring gets +1 refcount from the
substring, and it acts like a view into the superstring. To make
substrings like this, use the substring_with_shared_superstring() API.
One caveat:
- String does not guarantee that the underlying data is null-terminated
like DeprecatedString does today. While this was nifty in a handful of
places where we were calling C functions, it did stand in the way of
shared-superstring substrings.
2022-12-01 12:27:43 +00:00
|
|
|
|
2021-04-11 09:31:30 +00:00
|
|
|
[[nodiscard]] ByteBuffer to_byte_buffer() const;
|
2018-10-10 09:53:07 +00:00
|
|
|
|
2021-04-11 09:31:30 +00:00
|
|
|
[[nodiscard]] StringView string_view() const;
|
2019-09-25 08:49:41 +00:00
|
|
|
void clear();
|
|
|
|
|
2021-05-30 22:58:07 +00:00
|
|
|
[[nodiscard]] size_t length() const { return m_buffer.size(); }
|
|
|
|
[[nodiscard]] bool is_empty() const { return m_buffer.is_empty(); }
|
|
|
|
void trim(size_t count) { m_buffer.resize(m_buffer.size() - count); }
|
2019-09-29 14:20:09 +00:00
|
|
|
|
2020-03-20 13:33:46 +00:00
|
|
|
template<class SeparatorType, class CollectionType>
|
2022-02-22 21:31:05 +00:00
|
|
|
void join(SeparatorType const& separator, CollectionType const& collection, StringView fmtstr = "{}"sv)
|
2020-03-20 13:33:46 +00:00
|
|
|
{
|
|
|
|
bool first = true;
|
|
|
|
for (auto& item : collection) {
|
|
|
|
if (first)
|
|
|
|
first = false;
|
|
|
|
else
|
|
|
|
append(separator);
|
2022-02-22 21:31:05 +00:00
|
|
|
appendff(fmtstr, item);
|
2020-03-20 13:33:46 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-10-10 09:53:07 +00:00
|
|
|
private:
|
2021-11-10 13:33:44 +00:00
|
|
|
ErrorOr<void> will_append(size_t);
|
2021-05-14 18:53:04 +00:00
|
|
|
u8* data() { return m_buffer.data(); }
|
2021-08-09 15:48:50 +00:00
|
|
|
u8 const* data() const { return m_buffer.data(); }
|
2019-01-18 02:27:51 +00:00
|
|
|
|
2021-12-26 00:42:58 +00:00
|
|
|
static constexpr size_t inline_capacity = 256;
|
2022-11-14 18:25:18 +00:00
|
|
|
Detail::ByteBuffer<inline_capacity> m_buffer;
|
2018-10-10 09:53:07 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
}
|
|
|
|
|
2022-11-26 11:18:30 +00:00
|
|
|
#if USING_AK_GLOBALLY
|
2018-10-10 09:53:07 +00:00
|
|
|
using AK::StringBuilder;
|
2022-11-26 11:18:30 +00:00
|
|
|
#endif
|