Canonical repo address is inconsistent with module path

[KateGo520]

The github.com/KillingSpark/sparkzstd repo used the module, but the module path is set to github.com/killingspark/sparkzstd.
This means that the canonical github repo address now conflicts with canonical go import packages.

It is now very easy for downstream consumers (which used GOPATH mode) to accidentally add imports to upper-case "github.com/KillingSpark/sparkzstd/..." packages. This will create many pitfalls and break the module users. They may encounter errors:

go: downloading github.com/KillingSpark/sparkzstd v0.0.0-20190429053545-8961c737b70e
go: github.com/KillingSpark/sparkzstd upgrade => v0.0.0-20190429053545-8961c737b70e
go get: github.com/KillingSpark/sparkzstd@v0.0.0-20190429053545-8961c737b70e: parsing go.mod:
        module declares its path as: github.com/killingspark/sparkzstd
                but was required as: github.com/KillingSpark/sparkzstd 

Solution

1. Fix the module path:
   Rename the module path to ”github.com/KillingSpark/sparkzstd”.
   https://github.com/KillingSpark/sparkzstd/blob/master/go.mod#L1

module github.com/KillingSpark/sparkzstd 

2. Tell the user in the README document to use "github.com/killingspark/sparkzstd" as import path.

[KateGo520]

@KillingSpark Could you help me review this issue? Thx :p

[KillingSpark]

I hate that capitalized letters in a github name cause this much trouble when using go, I had this issue a while ago with my own and others packages too.

I could fix this, but to be completely honest, I do not recommend to use this package but to use the one of klauspost here. It has better decompression performance and provides compression too.

[KateGo520]

@KillingSpark Thank you for your reply! I'll take a look at the other package you recommended. : D

[KillingSpark]

I should propably update the Readme with that disclaimer tbh :D

I do not recommend to use this package but to use the one of klauspost here. It has better decompression performance and provides compression too.