Consider adding a generalized transformation directive

Open
#147 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
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
compilers

Research direction

Start by reviewing issue #119 and tracing the existing no_case work referenced here. Determine the API and implementation scope for a generalized transformation directive supporting input-only and input-plus-target transformations; the work is done when that design is implemented and validated for both forms.

Written by the indexing model from the issue text.

Description

From #119:

Maybe something for the future: there's a lot of effort in the code to get no_case working, and in
the end it's all about applying case folding. What about having a transformation-directive letting
users plug-in their own transformations for input and target:

transform( _input_transformation_ )[ parser ]
transform( _input_transformation_, _target_transformation_ )[ parser ]

Dominant language
C++
Stars
182
Forks
28
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 boostorg/parser

All issues in boostorg/parser

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.