scala / scala/scala-parser-combinators
ParseResult and its subtype are members of scala.util.parsing.combinator.Parsers
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 679
- Forks
- 131
- Avg merge
- 8h 25m
- Merged PRs (30d)
- 3
Description
ParseResult and its subtype are members of scala.util.parsing.combinator.Parsers. Why? This limits the ability to write code using ParseResult without any added benefit as far as I can see.
E.g. I would like to define a scalatest Matcher. I have to wrap it now into a scope, parameterized by a Parsers instance or I have to redefine the Matcher in every test case.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading scala.util.parsing.combinator.Parsers and its ParseResult subtype definitions. Determine how ParseResult is coupled to a Parsers instance and what API change would let callers use it independently without losing existing parser-combinator behavior. Done means the requested standalone use is supported with a clear compatibility decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100