Conversation
| (resultMay, ws) <- runLogger' . runExceptT . flip runReaderT P.defaultOptions $ do | ||
| ((P.Module ss coms moduleName elaborated exps, env), nextVar) <- P.runSupplyT 0 $ do | ||
| desugared <- P.desugar externs [P.importPrim m] >>= \case | ||
| env <- fmap fst . runWriterT $ foldM P.externsEnv P.primEnv externs |
There was a problem hiding this comment.
This builds the env for every compilation, right? Is it possible to build this once and reuse it?
There was a problem hiding this comment.
Ah of course, yes it does.
|
With this merged, are there any steps we should take to deploy the 0.13.6 version, or is it not quite ready for that? |
|
I've deployed this to the DigitalOcean droplet which I intend to be the new home for Try PureScript, and it seems to work! You can try it out by adding the following lines to your The only thing left to do is to update the gists: the main one still has links to all of the different backends, which no longer exist, so these links won't do anything, and a couple of the other ones have references to library functions which no longer exist, like I am coming to think that using gists for the examples is a bit awkward, since you can't do pull requests on them and access control on gists is not really a thing either. I think it would be ideal to move them inside the repo, although of course we should continue to support loading code from gists. I'll open a new issue for this. |
|
Ah! I hadn’t realized Try PureScript wasn’t already pointing at the new box. And I think version controlling the stable examples in this repository is a good idea. |
|
For now, I've just updated the gists. I think I'll switch the DNS over tomorrow unless anyone notices anything else that's broken :) |
|
Oh, we should probably fix #165 first too. |
No description provided.