Optimized Stringize/Latexize/ToSympy

Open
#1,415 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp

Research direction

Start by reviewing the Stringize, Latexize, and ToSympy implementations, then read the related discussion in #392. Done means the v3 API direction for reducing string allocations and the appropriate StringBuilder or alternative approach are agreed and documented.

Written by the indexing model from the issue text.

Description

Proposal

Using this many strings is suboptimal. Passing a StringBuilder (are there more efficient alternatives?) around would be more optimal. This changes the API surface so is v3 work. Related: #392

Dominant language
C#
Stars
832
Forks
79
Avg merge
3h 11m
Merged PRs (30d)
357

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from asc-community/AngouriMath

All issues in asc-community/AngouriMath

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.