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
There are two pretty obvious choices: file-path->*config-try-m seems too "wordy".
But file-name->*config Is ambiguous since it doesn't specify the context - just says that there is one.
(defmacroexception-of?"Construct predicate function for testing exception monad value. The predicate returns true if the monad contains `exc/failure` or if `exc/success` wraps value satisfying PRED predicate."
[pred]
`(fn [*val#]
(and (exc/exception? *val#)
(if (exc/success? *val#)
(m/bind *val# ~pred)
true))))
(defn-specfile-name->*config (exception-of? valid-config?)
[f-name file?]
...)
It should be better than adding "type" info into doc-string since the return value is validated by Orchestra's instrument so it won't go stale.
And Emacs doc thingy displays definition un-expanded so it's immediately apparent what kind of context is used.
But mb it's an overkill. 🤔
I haven't found any naming recommendation in the docs.
The text was updated successfully, but these errors were encountered:
How
def
/defn
s should be named?There are two pretty obvious choices:
file-path->*config-try-m
seems too "wordy".But
file-name->*config
Is ambiguous since it doesn't specify the context - just says that there is one.I ended up using Orchestra for exception monad:
It should be better than adding "type" info into doc-string since the return value is validated by Orchestra's
instrument
so it won't go stale.And Emacs doc thingy displays definition un-expanded so it's immediately apparent what kind of context is used.
But mb it's an overkill. 🤔
I haven't found any naming recommendation in the docs.
The text was updated successfully, but these errors were encountered: