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

backport #42 to 0.5.x (Correctly handle compressing empty slice), handle decompressing empty byte slice #50

Merged
merged 3 commits into from
Jan 16, 2019

Conversation

elijahandrews
Copy link
Contributor

@elijahandrews elijahandrews commented Jan 10, 2019

Backports #42 to 0.5.x. Also makes decompressing an empty byte slice consistent with the 1.x version (by retuning ErrEmptySlice)

@elijahandrews elijahandrews requested a review from Viq111 January 10, 2019 23:11
@elijahandrews elijahandrews changed the title backport #42 to 0.5.x (Correctly handle compressing empty slice) backport #42 to 0.5.x (Correctly handle compressing empty slice), handle decompressing empty byte slice Jan 10, 2019
@elijahandrews
Copy link
Contributor Author

elijahandrews commented Jan 11, 2019

I ran into a bit of cgo weirdness; in some of my application code I was getting panics saying cgo argument has Go pointer to Go pointer with a []byte argument. It looks like I hit this issue, and need to give cgo a bit more help.

I tried to capture the panic in a test but wasn't able to get it working; I might be missing some cgo magic, @Viq111 any ideas?

@elijahandrews elijahandrews merged commit 0013387 into 0.5.x Jan 16, 2019
@Viq111 Viq111 deleted the elijah/fix-empty-0.5 branch January 31, 2020 16:24
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