New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement 'is parsed' #177
Comments
Blocking on #174. |
should example:
(yes, I know, 007 doesn't have adverbs. Doesn't really matter) |
The category information, for better or worse, goes on the name of the identifier:
Currently leaning towards not allowing |
When you pass a sub as an argument (etc), the name changes. Which is really what makes this be. I think it makes sense that |
No longer blocking on #174, seeing as we have regexes now. 🎉 |
Yes, what you're saying is true. And I'm not fundamentally opposed to making One story that's missing currently for |
Now that we have regexes, I would like us to make
I haven't tried this myself, nor thought about what it would take. But clearly something needs to be installed somewhere. Probably a decent starting point is the operators, which are an open set and which can be installed. I'll accept PRs on this. If it's still open in a week or so, I'll try it myself. 😄 |
Not promising anything again, but it also sounds interesting. Should Should there be a |
Yes, but note that that in itself has no observable effect except to change what the parser parses. There's no introspection into the
That could work, yes. (Though, again, I haven't thought deeply about it.) The thing to make sure is that things behave sanely with the old, hard-coded statement types. |
Behind a feature flag.
The minimum viable feature would be enough to close this issue.
The text was updated successfully, but these errors were encountered: