Skip to content

Conversation

@ShadowOfHeaven-Me
Copy link
Contributor

Basically it. Not sure why I can't disregard my the previous pr changes, but whatever, the current origin should have the exact same code

Copy link
Collaborator

@booky10 booky10 left a comment

Choose a reason for hiding this comment

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

Additionally, it may also make sense to move this varint read/write implementation to the ByteBufOperator implementations to prevent way too many getter calls

@booky10 booky10 changed the title Optimized readVarInt() Velocity's varint reading/writing optimizations Dec 22, 2024
@ShadowOfHeaven-Me
Copy link
Contributor Author

ShadowOfHeaven-Me commented Feb 3, 2025

...why did this commit here

Nevermind that, fixed it

@ShadowOfHeaven-Me ShadowOfHeaven-Me force-pushed the 2.0 branch 2 times, most recently from 21f7324 to 94d4d80 Compare February 3, 2025 20:27
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.

3 participants