Skip to content

(fix): small typo in blanket-implementations.md #34

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.

Sign up for GitHub

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

Open
humb1t wants to merge 1 commit into
base: main
Choose a base branch
from
Open

(fix): small typo in blanket-implementations.md #34

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/blanket-implementations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -218,10 +218,10 @@ such feature has to be carefully considered to ensure that no inconsistency can

Due to potential conflicting implementations, the use of blanket implementations offer
limited customizability, in case if a context wants to have a different implementation.
Although a context many define its own context-specific provider to override the blanket
Although a context may define its own context-specific provider to override the blanket
provider, it would face other limitations such as not being able to implement other traits
that may cause a conflict.

In practice, we consider that blanket implementations allow for _a singular context-generic provider_
to be defined. In future chapters, we will look at how to relax the singular constraint,
to make it possible to allow _multiple_ context-generic or context-specific providers to co-exist.
to make it possible to allow _multiple_ context-generic or context-specific providers to co-exist.