Skip to content
This repository has been archived by the owner on Dec 17, 2020. It is now read-only.

Deal with half-baked effects: Coroutine, CutFalse and NonDet #10

Open
trskop opened this issue Feb 2, 2017 · 7 comments
Open

Deal with half-baked effects: Coroutine, CutFalse and NonDet #10

trskop opened this issue Feb 2, 2017 · 7 comments

Comments

@trskop
Copy link
Member

trskop commented Feb 2, 2017

IMHO, these effects aren't production ready. This was decided on today's session where @liskin, @xkollar, @Siprj, and I participated.

@trskop
Copy link
Member Author

trskop commented Mar 6, 2017

Alternative to removing an effect is to find a more practical definition. For example Coroutine could be useful, but its current definition is a proof of concept, and not a practical effect.

@xkollar
Copy link
Member

xkollar commented Mar 10, 2017

Also NonDet does not feel right...

@trskop
Copy link
Member Author

trskop commented Mar 12, 2017

We should look into extensible-effects, they seem to have figured some things out already.

@trskop trskop mentioned this issue Mar 17, 2017
@trskop trskop changed the title Hide half-baked effects: Coroutine and CutFalse Deal with half-baked effects: Coroutine, CutFalse and NonDet Mar 17, 2017
@trskop
Copy link
Member Author

trskop commented Mar 17, 2017

I think that PR #25 made Coroutines much more useful for real applications.

@spacekitteh
Copy link

@xkollar how does NonDet not feel right?

@xkollar
Copy link
Member

xkollar commented May 12, 2017

@spacekitteh: I would expect something with that name to behave more like list. Or do I miss something obvious?

@spacekitteh
Copy link

It's an implementation of a non-biased nondeterminism monad. See here.

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

No branches or pull requests

3 participants