Comments (5)
Should have been clear that I'm asking @ptersilie for thoughts.
from grmtools.
Does l.end().unwrap_or_else(|| l.start())
just return l.start()
, which then makes &input[
return an empty string?
Maybe we can add a method l.was_inserted_by_error_recovery()
that allows users to easily check if a lexeme is real or not. Or we add a function l.get_from_input(&input)
, which returns ""
if the lexeme was inserted by error recovery, and then tell users to use that instead of indexing the input themselves?
from grmtools.
The inserted
function allows you to tell if a lexeme was inserted by error recovery or not. My worry is that people will forget to test for that, then they'll do something like lexeme.end()
and be surprised that they end up with a zero length lexeme (for a lexeme definition that seemingly could never be zero length). I'm just not sure if I'm being unduly paranoid or not.
from grmtools.
I think we can't reasonably worry about everything the user might forget, especially if that means we make the life of less forgetful users more difficult by forcing them to use workarounds like l.end().unwrap_or_else(|| l.start())
. I rather have end/start
return 0 if the lexeme was inserted. I'm sure users will quickly remember that these are inserted lexemes when they get zero length ones.
from grmtools.
OK, I'll raise a PR.
from grmtools.
Related Issues (20)
- Order of execution of grammar statements? HOT 7
- Bug in grmtools documentation - traits not displaying required method names HOT 12
- Is there a way to avoid global variables for compile time data structures? HOT 5
- Request for example of handling string literals in lexer HOT 2
- error when using fake UMINUS token in %prec directive HOT 9
- GDB Support? HOT 5
- Add support for comments in lrlex files HOT 3
- Explain why Copy is required for a type specified %parse-param HOT 7
- Nondeterministic generation of Rust code HOT 2
- Support lex-style definitions HOT 1
- Trying to replicate `tinylang.yy` and `tinylang.l` syntax with `nimbleparse` HOT 5
- Weird that `nimbleparse` works on `java7.y` `java7.l` even though the `GT` symbol in both is different. HOT 1
- Online Yacc/Lex editor/tester HOT 6
- Detailed debug info for reduce/reduce shift/reduce errors? HOT 27
- Docs Question - Optional Prefix to Regular Expressions HOT 5
- lrpar lose info about debug HOT 7
- nimbleparse:Suggestions for outputting information HOT 5
- lrlex: match beginning of line HOT 4
- lrpar:%prec not followed by token name HOT 11
- lpar:Unused rule HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from grmtools.