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
I usually use Type, Implementations, Trait Implementations (similar to the Rust docs) in imap-types and imap-codec. In imap-flow it's not always consistent. I think this could be our default. But, in the end, let's use what makes most sense for a specific situation :-)
Type
,impl
, andimpl Trait
orderingType
,Implementations
,Trait Implementations
(similar to the Rust docs) inimap-types
andimap-codec
. Inimap-flow
it's not always consistent. I think this could be our default. But, in the end, let's use what makes most sense for a specific situation :-)Task
sFetch
vsFetch{Single,Many}
clone()
s required due toTask
traitseq
anduid
...Data
data structuresSome guidance about implementing
Task
s (potentially useful for docs) ...Data
Data
emitting awarn!
ing (using structured values)Data
when there is a code with the same meaning inStatus
emitting awarn!
ing (using structured values)The text was updated successfully, but these errors were encountered: