Skip to content

Feature: Implement a lexer that uses UTF-8 #75

Description

@mf366-dev

The Vision

A lexer that uses UTF-8 is a necessity because it would make the lexing process faster and UTF-16 is overkill anyway.

The Problem

Slowness and the need for heap allocations (strings are not UTF-8).

The Solution

A custom lexer, titled Utf8Lexer, which implements interface IUtf8Lexer.

Benefits

Reduction of edge cases and heap allocations across the projects.

Potential Drawbacks

Added complexity.

User Impact

Users who need the best performance possible really need this feature.

Related Context

The PR that added this is #74, but said PR did not test the changes made.

Metadata

Metadata

Assignees

Labels

Kind/FeatureIntroduces a brand-new capability that expands the project further.Scope/APIChanges to the API.Scope/PerformanceChanges that affect performance in a positive manner.Scope/UXUser experience content.

Fields

Effort

E: Medium

Platform

Desktop/LinuxDesktop/WindowsDesktop/macOSDesktop/BSDMobile/AndroidMobile/iOSWeb/BrowserWeb/WASMOther

Projects

Status
Testing

Relationships

None yet

Development

No branches or pull requests

Issue actions