duesee / duesee/smtp-codec

Figure out guidelines for misuse-resistant types.

Open
#8 2 comments 0 reactions 0 assignees View on GitHub
documentation help wanted
Dominant language
Rust
Stars
7
Forks
3
PR merge metrics
No merged PRs in 30d

Description

Having misuse-resistant types is (mostly) an all or nothing approach. Thus, the first thing would be to agree on this approach. The second thing would be to document it. More specifically, we would start to call the possibility to instantiate an invalid type a bug and treat it like so, i.e., resolve it.

Sometimes, however, there are many options to tighten a type with different pros and cons and it may not be obvious what to do.

There are also libraries for tight types that may be useful.

We should discuss and document this approach somewhere to reduce friction and make best use of this approach.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.