You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd want the evaluation of name to work resulting in:
main =dolet name ="codygman"-- >>> name-- codygmaninpure()
This would require bringing all bindings up to that point into scope. Typically I copy paste definitions in ghci like:
> let name = "codygman"
> name
I can see how this could be complex and have some edge cases, but the value of it would be immense especially for new Haskell users.
In fact this request comes because I was making an intro video "0 to Haskell ide in 5 minutes" type video and this feature was going to be the sort of centerpoint/ending to that video.
This would allow not really needing to use anything but haskell-language-server for development as well instead of having to open ghci for many cases. Regardless of whether that's always better, I think it's a good option to have.
I think this might be blocked or more difficult to implement if the current implementation isn't using -fexternal-interpreter as described here.
Given this:
I'd want the evaluation of name to work resulting in:
This would require bringing all bindings up to that point into scope. Typically I copy paste definitions in ghci like:
I can see how this could be complex and have some edge cases, but the value of it would be immense especially for new Haskell users.
In fact this request comes because I was making an intro video "0 to Haskell ide in 5 minutes" type video and this feature was going to be the sort of centerpoint/ending to that video.
This would allow not really needing to use anything but haskell-language-server for development as well instead of having to open ghci for many cases. Regardless of whether that's always better, I think it's a good option to have.
I think this might be blocked or more difficult to implement if the current implementation isn't using
-fexternal-interpreter
as described here.related: #94 #191 #51
The text was updated successfully, but these errors were encountered: