-
-
Notifications
You must be signed in to change notification settings - Fork 117
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
Worth adding some subset of stdlib Logging? #536
Comments
|
Ah; right you are. I never think to check for unexported functionality from Compat... |
All implemented functionality should be listed in Compats README. |
Yes, it is there. I don’t make a habit of reading the README file looking for unexported functionality either. Will do next time. Thanks!
… On Apr 24, 2018, at 3:25 PM, Fredrik Ekre ***@***.***> wrote:
I never think to check for unexported functionality from Compat...
All implemented functionality should be listed in Compats README.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A more refined version of (e.g.)
would make it easier to write code that works on v0.6 and v0.7/1.0, or would the recommendation be to import MicroLogging or some other framework on v0.6?
The text was updated successfully, but these errors were encountered: