Skip to content

Conversation

Cluster444
Copy link

Rebased from #2913 into main

@tenderlove tenderlove self-requested a review December 2, 2024 18:40
Copy link
Member

@tenderlove tenderlove left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this looks good. The arena implementation seems fine, I left a few minor commit suggestions but I don't see any actual problems.

@jhawthorn do you mind taking a look at this (if you have time)? Otherwise I'm going to merge it.

* #endif
* ```
*/

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change

}
case PM_TOKEN_QUESTION_MARK: {
context_push(parser, PM_CONTEXT_TERNARY);

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change

.warn_mismatched_indentation = true
};

// TODO: find a better starting size
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

4k is probably a fine starting size, maybe we can add some logging later and figure out a better start.


*stack = current->prev;
xfree(current);
// xfree(current);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we just delete this?

@kddnewton
Copy link
Collaborator

@tenderlove make sure you don't merge this before we get this working in ruby/ruby using the new API, otherwise this is going to break a bunch of stuff. I've been holding off on merging this because I want to make sure we can do some benchmarking on both speed and memory from within CRuby before we go this route, since it's a such an invasive change.

@kddnewton kddnewton mentioned this pull request Jan 23, 2025
@kddnewton
Copy link
Collaborator

I'll start testing this in ruby/ruby and see what changes are necessary. In the meantime I'm going to label this PR as "blocked" just to indicate that it should not be merged until it is fully tested over there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants