You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
go.mod defines the package via module logdy when it should be module github.com/logdyhq/logdy-core. Attempting to import it from another module then results in an error:
github.com/logdyhq/logdy-core/ring: github.com/logdyhq/logdy-core@v0.11.0: parsing go.mod:
module declares its path as: logdy
but was required as: github.com/logdyhq/logdy-core
The text was updated successfully, but these errors were encountered:
Hi, thanks for calling that in, I'll look into that. Can I ask about your use case of importing Logdy from another module? I was thinking about making it easier to embed Logdy into a Go app.
I found your ring package in a Google search, which looked like a clean implementation of a typed ring buffer, so I was going to try it. However I found that I wanted to clean up with API a bit (eg, replace most error result types with bool), so it probably makes more sense to fork it anyway. Unless you are open to considering contribution PRs?
go.mod
defines the package viamodule logdy
when it should bemodule github.com/logdyhq/logdy-core
. Attempting to import it from another module then results in an error:The text was updated successfully, but these errors were encountered: