Closed tavisrudd closed 10 years ago
It's just our convention for private: Python on the brain, etc.
Would forceResolve
have the same signature and behaviour? Are you thinking of a default implementation on Resolvable
? If so, why not just put the function alongside Resolvable
but outside the typeclass?
Would forceResolve have the same signature and behaviour? Are you thinking of a default implementation on Resolvable? If so, why not just put the function alongside Resolvable but outside the typeclass?
I guess providing forceResolve
outside the typeclass would make sense actually. And yes, exactly what you've written, without the underscore. Hahaha. :)
Sorry for the delay - personal circumstances permitting I'll look at this again later in the week.
initCall
andunsafeInitCall
inD.P.P.ManagedProcess.Internal.Types
were both vulnerable to pattern match failure when passed an unresolvableAddressable
. It is more helpful to the developer / debugger to die withunresolvableMessage addressable
.