This repository was archived by the owner on Jan 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 170
doesnt work in parallel usage (multiple goroutines) #26
Comments
Is there a written rule out there that all packages must be concurrency-safe? |
so when using this package, I can't using goroutine? |
@gorhill I suppose so else Golang doesn't guarantee anything. |
kyoh86
pushed a commit
to wacul/batch
that referenced
this issue
Aug 2, 2017
This commit is the patch for gorhill/cronexpr#26.
dadgar
added a commit
to dadgar/cronexpr
that referenced
this issue
Sep 15, 2017
This PR allows concurrent calls to Parse. Further it makes the test be part of the same package. Fixes gorhill#26
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In parsing, global package variable layoutRegexp is changing. It is map, so usage in multiple gorountines causes map concurrent write error.
The text was updated successfully, but these errors were encountered: