Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Is there a reason boost::parser::none::fail() is a runtime error, not a compile time error?

Open
#273 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
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
compilers

Research direction

The issue names boost::parser::none::fail(); start by locating its implementation and the surrounding parser error-handling code. Compare the current runtime failure with the proposed static_assert approach and determine whether compile-time rejection is valid. Done means documenting the reason or agreeing on a concrete change.

Written by the indexing model from the issue text.

Description

Hi,

when I mess up my parsers, sometimes I run into none::fail. This is a runtime error. Why not a compile time error with static_assert(false) or static_assert(!std::is_same_v<T,T>) to force late evaluation?

Is there a reason I am missing?

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.