-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
avoid kind type dispatch bugs in tuple_type_head and tuple_type_tail #27776
Conversation
will merge tomorrow if there are no objections |
(let's make sure nanosoldier doesn't object) @nanosoldier |
I didn't follow along what issues this is solving, but ... can't they be tested for? |
Your benchmark job has completed - possible performance regressions were detected. A full report can be found here. cc @ararslan |
Definitely, it'd be great to have a non-Cassette MWE here, I just haven't figured one out yet. From the OP:
If you're curious, here's a Cassette-based one I posted: #27736 (comment) Looks like Nanosoldier doesn't like the new implementations...maybe adding a |
@nanosoldier |
Had to restart the server. @nanosoldier |
Your benchmark job has completed - possible performance regressions were detected. A full report can be found here. cc @ararslan |
Cool, the |
This is a much more narrowly-scoped alternative to some of the tuple code changes that were originally in #27736 (i.e. c16a109).
It would still be nice eventually to figure out alternative implementations for c16a109, since switching to
fieldtype
is more sound in general (see discussion from #27736). However, for now, this much more palatable change works around the problems that are blocking Cassette.Unfortunately, I don't have a non-Cassette test case for these bugs yet; they're pretty hard to work out MWEs for.