-
Notifications
You must be signed in to change notification settings - Fork 41
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
Other file accessors besides appender? #24
Comments
Sorry, I totally missed this message 😱 Can you please clarify on what Currently, |
Yes, I think I was in "debug mode" and wanted an "overwrite, don't append" mode which did not (does not ?) exist yet. It seems that it is standard POSIX semantics, so should be add a simple "destructive" file accessor? |
Thanks for the clarification 👍 |
Yes that is close to what I had in mind. If it were me I'd also add a convenience function with a different name that just calls this one with |
Yeah, you are right -- I tried to keep the |
Okay, so I think this requires dropping the "appender" term from the overall design as well: And the I guess that sounds OK? I mean the Sorry for the wall of text ... but after messing up with the original 3-4 terms on which the whole design was built, probably it's better to spend some extra time to do this right after all. |
Referencing the main |
Didn't mean to imply cascading changes and wholesale renaming. |
merging now and will generalize the file appender a bit further at #31 |
Maybe I am being dense but while
log_appender(appender_file(someFilename))
worked great, I think I'd also like a (trivial)
create_file(...)
oroverwrite_file()
. Is there a common idiom in the other logging frameworks?logger
is ❤️ though. Really nice so far.The text was updated successfully, but these errors were encountered: