Skip to content
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

Put 1.9-dev on master #2038

Merged
merged 300 commits into from
Jan 10, 2019
Merged

Put 1.9-dev on master #2038

merged 300 commits into from
Jan 10, 2019

Conversation

rmosolgo
Copy link
Owner

Still a few items to knock out before releasing (#1884), but I think things are stable enough to make this a default.

We can always backport changes to 1.8 if needed.

rmosolgo and others added 30 commits August 28, 2018 13:10
Change the default behavior of the encoder to use `urlsafe` versions
[Language::Visitor] use method-based visit handlers
Don't pass resolver objects to field extensions
Change the default behavior of the encoder to use `urlsafe` versions
rmosolgo and others added 28 commits December 13, 2018 12:27
Fix introspection on interpreter
Add AST::Visitor#previous_field_definition
[1.9] Look for perf wins in AST analysis
…thods

Add Field#resolver_method, remove `super` on field methods
Add warning for proc-based visitors
This allows better reporting of codes without the need to use `to_h`. It's also better for subclasses as they can modify if they need to. Which for fine grained reporting they would want to.

I'm sure I had good reasons to make this private originally, but use cases now show this would be a much better solution.
Allow code to be accessed outside of the errors
@rmosolgo rmosolgo merged commit 7eb62c2 into master Jan 10, 2019
@rmosolgo rmosolgo deleted the 1.9-dev branch July 30, 2019 19:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants