issues
search
tzlaine
/
parser
A C++ parser combinator library.
Boost Software License 1.0
70
stars
12
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
How to use the default error handler?
#80
akrzemi1
closed
5 months ago
5
How to skip comments without producing attributes?
#79
akrzemi1
closed
5 months ago
4
state of the output argument upon unsuccessful parse
#78
akrzemi1
closed
5 months ago
2
Rule parser definition doesn't validate the attribute type
#77
akrzemi1
closed
5 months ago
13
Strange int-to-string attribute conversions
#76
akrzemi1
closed
5 months ago
5
How to define a rule parser with an empty attribute?
#75
akrzemi1
closed
5 months ago
1
The interface for defining rules is uncomfortable
#74
akrzemi1
closed
5 months ago
4
Document `BOOST_PARSER_SUBRANGE` in configuration and optional features
#73
tzlaine
closed
5 months ago
0
Parsers don't have names but diagnostic messages
#72
akrzemi1
closed
5 months ago
3
Shorter way of defining a rule?
#71
akrzemi1
closed
5 months ago
3
A single-header version?
#70
akrzemi1
closed
5 months ago
2
Introduce a macro a la `BOOST_PARSER_DETAIL_TEXT_SUBRANGE`, and use it in the `parser` code too
#69
tzlaine
closed
5 months ago
0
docs: fix incorrect "next section"
#68
akrzemi1
closed
5 months ago
1
optional sequence returns
#67
akrzemi1
closed
5 months ago
8
Type trait for parser's attribure
#66
akrzemi1
closed
5 months ago
2
Document the regularity requirement
#65
tzlaine
closed
5 months ago
0
Consider search(), split(), and other algorithms that might take parsers
#64
tzlaine
closed
5 months ago
0
add directive `defaulted`
#63
akrzemi1
closed
5 months ago
1
Cleaner description of attribute combination
#62
akrzemi1
closed
5 months ago
1
Update docs (incl. rationale) based on discussion in #60
#61
tzlaine
closed
5 months ago
0
"optional sequence" attribute should collapse to vector
#60
akrzemi1
closed
5 months ago
7
Need an example using `raw[]` and `string_view[]`
#59
tzlaine
closed
5 months ago
0
Add doc section on writing parsers.
#58
tzlaine
closed
5 months ago
0
Should `lexeme` turn `tuple<char...>` into `string`?
#57
akrzemi1
closed
5 months ago
1
shorter error messages?
#56
akrzemi1
opened
5 months ago
7
How to parse into string a small token with a constraining pattern?
#55
akrzemi1
closed
5 months ago
1
sequence of `ascii` parsers should render a string
#54
akrzemi1
closed
5 months ago
1
Optional support for Boost.Optional?
#53
akrzemi1
closed
5 months ago
7
double-nested aggregate attribute not working
#52
akrzemi1
closed
6 months ago
2
Add a user-configurable macro that controls the max size of an aggregate struct
#51
tzlaine
closed
6 months ago
0
Nested aggregate structures do not work
#50
akrzemi1
closed
6 months ago
4
Consider adding support for constructing `class` types from tuples, as a generalization of the tuple -> aggregate construction we do now
#49
tzlaine
closed
5 months ago
0
Document struct member size limit of 50.
#48
tzlaine
closed
6 months ago
0
parsing to `vector<aggregate>` doesn't work
#47
akrzemi1
closed
6 months ago
1
Introduce `%` earlier in the docs, and stop writing `x >> *(',' >> x)`
#46
tzlaine
closed
6 months ago
0
Parsing to user-defined types doesn't work
#45
akrzemi1
closed
6 months ago
1
Add `no_case[]` directive, backed by Unicode case folding
#44
tzlaine
closed
6 months ago
0
Error handlers are underdocumented
#43
akrzemi1
closed
5 months ago
4
Docs: describe `operator>`
#42
akrzemi1
closed
5 months ago
0
Docs: what is a parser?
#41
akrzemi1
closed
5 months ago
5
Fix spelling of hexadecimal
#40
sehe
closed
6 months ago
1
Rule Parsers require more explanation
#39
akrzemi1
closed
5 months ago
3
typo in the docs "Ready" instead of "read"
#38
mclow
closed
6 months ago
1
Remove needless inclusion of `<coroutine>`
#37
tzlaine
closed
6 months ago
0
How does parsing to `vector<string>` work?
#36
akrzemi1
closed
6 months ago
3
Describe backtracking
#35
akrzemi1
closed
5 months ago
3
Should I use `ascii` parsers?
#34
akrzemi1
closed
6 months ago
0
Consider using Boost.PFR
#33
akrzemi1
closed
6 months ago
1
Use implementation from Describe's pp_for_each.hpp for `BOOST_PARSER_DEFINE_RULES`
#32
tzlaine
closed
6 months ago
0
undefined `str` in the description of `parse`
#31
akrzemi1
closed
6 months ago
3
Previous
Next