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

Repl #17

Open
heades opened this issue Jul 19, 2016 · 6 comments
Open

Repl #17

heades opened this issue Jul 19, 2016 · 6 comments
Assignees
Labels
Milestone

Comments

@heades
Copy link
Member

heades commented Jul 19, 2016

Implement repl. See grady implementation for inspiration.

@heades heades added the TODO label Jul 19, 2016
@heades heades added this to the REPL milestone Jul 19, 2016
@tattymennis
Copy link
Collaborator

Should I program a top-level let expression for the Repl? It would be very useful in testing (and using) the language, but might conflict with the let term parsers. If so, I could change the reserved "let" to be "letu" and "lett" respectively.

@heades
Copy link
Member Author

heades commented Jul 22, 2016

On Jul 22, 2016, at 9:41 AM, Matthew Tennis [email protected] wrote:

Should I program a top-level let expression for the Repl? It would be very useful in testing (and using) the language, but might conflict with the let term parsers. If so, I could change the reserved "let" to be "letu" and "lett" respectively.

Yes, we defiantly want the top-level let expression for the repl. However, we should be able to keep them all
named let, because their different parsers. Try and make it work.

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub #17 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/ABZ7mGPujJCvaHg6BLVA0HAM68JBJxRqks5qYMibgaJpZM4JP9tU.

@tattymennis
Copy link
Collaborator

Gotcha, I know how I'll do it.

@tattymennis
Copy link
Collaborator

I've implemented the ability for the Repl to take in a top-level let variable and print it from the internal queue. However, I need to handle the error if that variable isn't in the queue. My intuition is to return with an Either String Term and case split on the output of the function, but I'm having conceptual difficulties of using Either within a REPLExpr or REPLStateIO(). I'm familiar with Either and simple monads, but I don't fully understand the intricacies of working in the environment.

Can we go over some more advanced monad topics on Tuesday?

@heades
Copy link
Member Author

heades commented Jul 31, 2016

Yes, we can go over this on Tuesday. Unfortunately, I do not have time to meet
until then. Sorry. Talk to you more on Tuesday.

On Jul 31, 2016, at 1:21 PM, Matthew Tennis [email protected] wrote:

I've implemented the ability for the Repl to take in a top-level let variable and print it from the internal queue. However, I need to handle the error if that variable isn't in the queue. My intuition is to return with an Either String Term and case split on the output of the function, but I'm having conceptual difficulties of using Either within a REPLExpr or REPLStateIO(). I'm familiar with Either and simple monads, but I don't fully understand the intricacies of working in the environment.

Can we go over some more advanced monad topics on Tuesday?


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub #17 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/ABZ7mB4PHKyN5cuOBCGw_e1FkUZ_xYvNks5qbNmSgaJpZM4JP9tU.

@tattymennis
Copy link
Collaborator

No problem, sounds great. Thanks!

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

2 participants