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
When first building stdlib, it takes a while for the playground to respond because it takes a while to build stdlib. Building and running programs that use stdlib subsequently is faster because the stdlib is reused, at least for this running session of the backend server.
I wonder if it would be a good idea and easy to implement to pre-build any built-in libraries (for now just stdlib) at docker build stage, rather than at server run time?
The text was updated successfully, but these errors were encountered:
That's what I used in the first iteration but as @everythingfunctional stated it would mean that all the libraries are built which won't be useful if the user only imports some selected libraries.
When first building stdlib, it takes a while for the playground to respond because it takes a while to build stdlib. Building and running programs that use stdlib subsequently is faster because the stdlib is reused, at least for this running session of the backend server.
I wonder if it would be a good idea and easy to implement to pre-build any built-in libraries (for now just stdlib) at
docker build
stage, rather than at server run time?The text was updated successfully, but these errors were encountered: