Add io! macro
#5
Open
Conversation
This file contains hidden or 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
rlycx
force-pushed
the
io-macro
branch
2 times, most recently
from
057c2ed to
470c1ec
Compare
- Introduce `return x` to `pure(x)` transformation - Make `do` mandatory when performing a side-effect - Fix up a non-portable test
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.
Introduces the
io!macro, which allows users to composeIOeffects more easily.Some things are copied from Haskell verbatim, while other things have a touch more Rust to them. For example, whitespace is not significant in Rust, so everything must be semicolon-terminated (except for the last expression).
Future extensions could be to allow
?on functions that returnstd::io::Resultin let-bindings to allow lifting imperativeiofunctions into the monad in an ad-hoc fashion.Resolves #4.