Container-policy parameter for parse functions

Open
#235 0 comments 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

No files or tests are identified. Begin by locating the library's parse functions and determine how a policy type could define default containers without unnecessary conversions; done would require an agreed policy interface and coverage for the supported container choices.

Written by the indexing model from the issue text.

Description

Consider adding the option to provide a policy type parameter that specifies which containers the library should use by default (to minimize conversions and/or minimize verbosity - need for the user to specify his own preferences) like

struct containers
{
  template <typename T> using vector = boost::container::small_vector<T,...>;
  template <typename Key, typename Value> using ordered_map = boost::container::flat_map<....>;
};
Dominant language
C++
Stars
182
Forks
28
PR merge metrics
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.