-
Notifications
You must be signed in to change notification settings - Fork 21
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.
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
Design section #36
Merged
Merged
Design section #36
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nomisRev
approved these changes
Feb 24, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple of remarks, but we can address them subsequent PRs.
content/learn/design/contexts-f.md
Outdated
|
||
The signature of `traverse` shows another important part of the monadic style of effects, namely _higher-kinded types_. Since monads are types which take other types as parameters -- like `Option` or `Result` --, to provide utility functions that work over different monads one must have a way to refer to those types. In Scala this is made explicit by the number of underscores after the type name, like `F[_]` above; in Haskell this is not made explicit in the signature, but is still checked by the compiler. Even after decades from their inception, higher-kinded types are still considered an advanced feature, and haven't made their way into mainstream programming languages. | ||
|
||
The reason why Kotlin doesn't require higher-kinded types to provide similar abstraction is that the same functions which work over "regular" functions, like `map`, keep working when used in the coroutine world. Kotlin language designers have found, in my opinion, a great point in the design space, in which they can offer the same abilities but without the cost of such a complex feature. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we insert a small example here?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR brings a few articles published (or under publication) from 47's blog into a section about general design. The original sources are credited.
Note: @nomisRev's article about domain modeling was updated to talk about
value class
instead ofinline class
.