Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / fge/grappa issues and pull requests
#36 - Fixes #35
Pull Request -
State: open - Opened by jottinger almost 9 years ago
#35 - enforceVersion for build is too strict
Issue -
State: closed - Opened by jottinger almost 9 years ago
- 2 comments
#34 - Sample project mentioned from readme doesn't exists anymore
Issue -
State: open - Opened by sshikov about 9 years ago
#33 - Enforce java7 only when publishing artifacts
Pull Request -
State: closed - Opened by GUIpsp about 9 years ago
#32 - parsing errors
Issue -
State: open - Opened by a1dutch over 9 years ago
#31 - firstOf() ignores overridden fromStringLiteral(String)
Issue -
State: open - Opened by akirschbaum over 9 years ago
- 1 comment
#30 - anyOf(Characters.ALL) matches at end of input
Issue -
State: open - Opened by akirschbaum over 9 years ago
#29 - Static rule creates broken parser
Issue -
State: open - Opened by akirschbaum over 9 years ago
- 1 comment
Labels: bug
#28 - firstOf() fails for one-character String argument
Issue -
State: open - Opened by akirschbaum almost 10 years ago
- 1 comment
Labels: bug
#27 - Recursive rules passing different Var instances should be possible
Issue -
State: open - Opened by akirschbaum almost 10 years ago
- 1 comment
#26 - Infinite recursion regression
Issue -
State: closed - Opened by akirschbaum almost 10 years ago
- 7 comments
#25 - Typo in error message
Issue -
State: closed - Opened by akirschbaum almost 10 years ago
- 3 comments
#24 - Value stack is not cleared between ParseRunner.run() calls
Issue -
State: closed - Opened by hatstand0 almost 10 years ago
- 8 comments
Labels: bug
#23 - NullPointerException when adding an element to a collection inside rule method
Issue -
State: open - Opened by ghost about 10 years ago
- 1 comment
#22 - Label for rule is not applied by method, but works with annotation
Issue -
State: open - Opened by ghost about 10 years ago
Labels: bug
#21 - LineCounter can provoke a StackOverflowError in .toPosition()
Issue -
State: closed - Opened by fge about 10 years ago
Labels: bug
#20 - CharSequenceInputBuffer should use daemon threads to issue its LineCounter instances
Issue -
State: closed - Opened by fge about 10 years ago
- 1 comment
Labels: bug
#19 - Introduce BooleanVar, IntVar, LongVar, DoubleVar?
Issue -
State: open - Opened by fge about 10 years ago
Labels: enhancement, help wanted, question
#18 - Incorrect function names in error messages
Issue -
State: closed - Opened by akirschbaum over 10 years ago
- 1 comment
#17 - Using a boolean action variable for guarding rules fails with a NPE
Issue -
State: closed - Opened by kenwenzel over 10 years ago
- 10 comments
Labels: bug
#16 - New parsing run/parsing result API
Issue -
State: open - Opened by fge almost 11 years ago
Labels: enhancement, help wanted, planned
#15 - The relevance of `RecoveringParseRunner`?
Issue -
State: closed - Opened by fge almost 11 years ago
- 1 comment
Labels: help wanted, question
#14 - Eliminate the uses of `ProxyMatcher` when it is not needed
Issue -
State: open - Opened by fge almost 11 years ago
Labels: enhancement, planned
#13 - Should `null` really be allowed in `Var`?
Issue -
State: closed - Opened by fge almost 11 years ago
- 1 comment
Labels: help wanted, planned
#12 - Version 2.x.*: investigate the use of `invokedynamic`
Issue -
State: open - Opened by fge almost 11 years ago
Labels: help wanted, planned
#11 - Create an `InputBuffer` over a `Reader`?
Issue -
State: open - Opened by fge almost 11 years ago
Labels: enhancement, planned
#10 - More Unicode related rules
Issue -
State: open - Opened by fge almost 11 years ago
Labels: enhancement, planned
#9 - Spurious compiler warnings due to @Nullable annotations
Issue -
State: open - Opened by akirschbaum almost 11 years ago
- 2 comments
Labels: enhancement
#8 - Allow parse warning messages
Issue -
State: open - Opened by akirschbaum almost 11 years ago
- 1 comment
Labels: enhancement
#7 - Allow custom parse error messages
Issue -
State: open - Opened by akirschbaum almost 11 years ago
- 1 comment
Labels: enhancement
#6 - Possibly contradicting parse error indicators
Issue -
State: closed - Opened by akirschbaum almost 11 years ago
- 5 comments
Labels: bug
#5 - Parse runners are not reusable
Issue -
State: closed - Opened by fge almost 11 years ago
- 1 comment
Labels: bug, wontfix
#4 - `BasicParseRunner` fails to account for parsing errors
Issue -
State: closed - Opened by fge almost 11 years ago
- 1 comment
Labels: bug
#3 - Longstanding bugs in generated ParseRunners
Issue -
State: closed - Opened by fge almost 11 years ago
- 1 comment
Labels: bug
#2 - CharSink closes its Writer after every .write() [was: provide alternative for deprecated TracingParseRunner.getLogs()]
Issue -
State: closed - Opened by chbussler almost 11 years ago
- 16 comments
Labels: bug
#1 - Parser generation crashes with BufferOverflowException
Issue -
State: closed - Opened by akirschbaum almost 11 years ago
- 5 comments