-
Notifications
You must be signed in to change notification settings - Fork 14
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
Haskell support #18
Labels
Comments
adrysn
added a commit
that referenced
this issue
Oct 23, 2016
adrysn
added a commit
that referenced
this issue
Oct 27, 2016
adrysn
added a commit
that referenced
this issue
Nov 1, 2016
adrysn
added a commit
that referenced
this issue
Nov 2, 2016
adrysn
added a commit
that referenced
this issue
Nov 2, 2016
* Default return type of Aeson's encode is lazy ByteString, which is incompatible with the prototype of haskell-zeromq's send function
adrysn
added a commit
that referenced
this issue
Nov 2, 2016
I still don't know about monad, but by using liftIO, we can print something to the console in any monad by lifting to IO monad
adrysn
added a commit
that referenced
this issue
Nov 2, 2016
Handling Monad is too confusing for me. I haven't figured out how to walk about among various monads yet, and this prevents me to write execution routine and intercepting std*. Instead, I will try to write a haskell code execution script with other languages (e.g. python):
|
adrysn
added a commit
that referenced
this issue
Nov 14, 2016
* Haskell code execution is handled in a python script * Delivered haskell code is saved in a temporary file and run by runhaskell command * stdout and stderr is captured by python's subprocess.run() and returned
adrysn
added a commit
that referenced
this issue
Nov 14, 2016
achimnol
added a commit
that referenced
this issue
Feb 24, 2017
adrysn
added a commit
that referenced
this issue
Oct 22, 2017
adrysn
added a commit
that referenced
this issue
Oct 22, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: