Skip to content

Update the GC tiered level from B to C.#4817

Merged
lum1n0us merged 1 commit intobytecodealliance:mainfrom
lum1n0us:fix/gc_tier_down
Mar 17, 2026
Merged

Update the GC tiered level from B to C.#4817
lum1n0us merged 1 commit intobytecodealliance:mainfrom
lum1n0us:fix/gc_tier_down

Conversation

@lum1n0us
Copy link
Contributor

Several known limitations have been exposed, and a few might impact the estimation when trying to integrate that feature into a product.

Several known limitations have been exposed, and a few might impact the
estimation when trying to integrate that feature into a product.
@TianlongLiang
Copy link
Contributor

@no1wudi do you have any thoughts on this? @lum1n0us and I don't have too much bandwidth working on syncing the implementation with the newest GC proposal. I wonder whether you will be interested/needed the newest GC proposal. If you are not interested either, I think it's safe for us to update the GC proposal to tier C(won't affected the fact the maintenance of existing parts) as this PR does.

@lum1n0us lum1n0us merged commit 87a8114 into bytecodealliance:main Mar 17, 2026
1 check passed
@lum1n0us lum1n0us deleted the fix/gc_tier_down branch March 17, 2026 05:04
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.

2 participants