-
Notifications
You must be signed in to change notification settings - Fork 6
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
Encode requests using Grammars #26
Comments
Are you suggesting using a grammar to replace
so that it isn't something that LOOKS like a function body but is actually just a param passed to a function? Because if so I am 100% in support of this. |
@masukomi |
Obviously the current way will still have to exist to keep backwards compatibility. |
this is early enough that i don't think it's bad to break backwards compatibility. a) there's hardly anyone using it b) it was pretty clear it was very early stages c) they can just pin it to the old version if it matters to them. I don't think it's worth maintaining tech debt indefinitely for such a small number of users and actual instances of the code in action. |
I'm thinking that maybe the grammar can translate to the current scheme. We'll see though. Still pretty up in the air on how we should approach this. |
Right now requests are encoded very naively, we can use grammars to make this better.
The text was updated successfully, but these errors were encountered: