Skip to content
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

Allow opt-out of unsafe methods #55

Closed
japgolly opened this issue Dec 20, 2014 · 3 comments
Closed

Allow opt-out of unsafe methods #55

japgolly opened this issue Dec 20, 2014 · 3 comments
Labels

Comments

@japgolly
Copy link
Owner

Opt-out of

  • setState
  • modState{,O,U}
  • state ← technically but this can stay
  • ==>
  • -->

Add:

  • IO[S]
  • S ⇒ IO[Unit]
  • S ⇒ S ⇒ IO[Unit]
  • Versions of above with ChangeFilter
@japgolly japgolly added the maybe label Dec 26, 2014
@japgolly japgolly changed the title Allow opt-out of unsafe methods, add more safe replacements Allow opt-out of unsafe methods Dec 26, 2014
@japgolly
Copy link
Owner Author

japgolly commented Jun 8, 2015

Reminder to future-me:

  1. You're soooooooooooo good-looking. -Z
  2. A good solution might be via modules: Define an Unsafe type. The unsafe module defines an implicit for Unsafe such that it's always satisfied. Could always go the other way and define 2 implicits in a safe module to prevent (by default) unsafety. ("unsafeness"?)

@japgolly
Copy link
Owner Author

japgolly commented Jun 8, 2015

Oh actually it would be best to be able to (at runtime) change schemes.
Tests I'd want unsafe.

@japgolly
Copy link
Owner Author

#145 supersedes this. We will soon have One Way (and it's not scalaz.IO).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant