[Feature]: ReadOnlySpan<char> across the board

[iXab3r]

Pre-submission Checklist

• I have read the README features list
• I have read the FAQ Wiki
• I have searched existing issues and this feature hasn't been requested
• I have verified this feature doesn't already exist in the package

Problem Statement

Migrating from ImGuiNet to Hexa.NET we've noticed that there are no overloads accepting ReadOnlySpan<char>, this makes migration more complex than it potentially could be

Methods like Utils.EncodeStringUTF8 and Utils.GetByteCountUTF8 are also working only with strings, yet underlying Encoding.UTF8 method do have ReadOnlySpan<char> overloads.

Proposed Solution

Hexa.NET.Utilities

• add overloads to Utils accepting ReadOnlySpan<char> - this is where the core logic will be moved
• existing methods working with string will use AsSpan() extension method on supplied strings. It does not allocate

Hexa.NET.ImGui

• same approach, my current understanding is that it will require mostly manual work in Manual/Functions/Functions.*.cs but please correct me if I am wrong

I have not digger deep enough yet into code generation part of the framework, I would assume same idea could be used there as well.

If you'll approve this I am happy to try to contribute

Alternatives Considered

Using ReadOnlySpan<byte> (and u8) is the most performant way of working with strings, but the tooling around it is very rough yet. If we're talking about software which tries to balance between convenience and performance, ReadOnlySpan<char> is usually the way to go.

Additional Context

No response

[JunaMeinhold]

Hi, i would suggest you move/link this issue to the HexaGen repo, because here isn't the right place for it. And also I'm working on the migration (#106) from the legacy version to mainline of this repo so it would take some while until i could add this feature. Please note I that i currently struggle with depression and it could take a while.

[JunaMeinhold]

Additionally, I'm aware of that the utf-8 tooling is partially missing which is why I added this to Hexa.NET.Utilities

byte* buffer = stackalloc byte[128];               // Use a stack-allocated buffer
StrBuilder builder = new(buffer, 128);            // Initialize a memory-safe builder
builder.Reset();                                  // Clear any previous content
builder.Append("Hello "u8);                       // Append UTF-8 literal
builder.Append(number);                           // Append number directly
builder.Append(" world!"u8);                      // Append more text
builder.End();                                    // Finalize the buffer
ImGui.Text(builder);                              //

It might be possible to some how integrate that with the string interpolation handlers but don't ask me how... didn't had the energy to look into it yet.