Cache results of matcher

Open
#536 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
rust
Domain
compilers

Research direction

The issue names no file or function, only the matcher, so first find where the transpiler invokes its matchers and how their results are consumed. Check whether the same match is recomputed for the same AST node. Done would mean repeated matcher queries reuse cached results while the generated Rust output stays unchanged. Ask the maintainers which matcher and which node key to cache before starting.

Written by the indexing model from the issue text.

Description

performance

Add a caching layer over the results returned by matcher to avoid useless deduction.

Dominant language
Rust
Stars
310
Forks
18
Avg merge
10h 18m
Merged PRs (30d)
125

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 Cpp2Rust/cpp2rust

All issues in Cpp2Rust/cpp2rust

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.