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
Since for golfing languages, most of the execution time is spent inside the implementations of the built-ins rather than the interpreter, a common golfing runtime doesn't have a huge advantage over a plain library of common built-ins. However, adding a debugger to the runtime would be a pretty big advantage over a library. While it's a pretty big task to undertake, we might want to start design the runtime with a debugger in mind, so it won't be too hard (or impossible) to add a debugger down the line. Thoughts?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Since for golfing languages, most of the execution time is spent inside the implementations of the built-ins rather than the interpreter, a common golfing runtime doesn't have a huge advantage over a plain library of common built-ins. However, adding a debugger to the runtime would be a pretty big advantage over a library. While it's a pretty big task to undertake, we might want to start design the runtime with a debugger in mind, so it won't be too hard (or impossible) to add a debugger down the line. Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions