servo/unicode-bidi

Make types generic over encoding

Open

#113 opened on Oct 30, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Rust (38 forks)github user discovery
help wanted

Repository metrics

Stars
 (87 stars)
PR merge metrics
 (PR metrics pending)

Description

See https://github.com/servo/unicode-bidi/pull/109

Currently we have BidiInfo and then utf16::BidiInfo types (with other similar duplication).

It would be nice if instead we had BidiInfo<T>, ParagraphInfo<T>, etc, which all used some trait input like TextInfo; rather than having duplicate types for everything. We might need some kind of UTF8 UTF16 marker type for this.

I don't have the time to do this myself but it would be really neat. Especially if we can extend stuff to UTF32 as well as WTF8 and other ill-formed UTF8.

Contributor guide

Research direction
Analyze the current codebase to understand the duplication of BidiInfo and UTF16 types, then design a generic trait based solution utilizing type parameters.
Tech stack
rust
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70