no way to see output

[sumeet]

you can't see the output (which in this case will be a number), or even intermediate values, without converting back into a string and printing it in the chat test window.

there should be another way, either some sort of script abstraction, or debugging.

should you have to wait for your program to reduce values, or call a logging function? or can that be part of the overall dev flow.

here are some ideas that i think demonstrate the direction i'm thinking in:

• Log function. It's generic (doesn't require a String, but any type works) and uses the ValueRenderer to print... somewhere. maybe inline next to the code, or to a separate log window. (and maybe the log window would have a backref to the code?)
• Support "scripts" which are like functions in that they're a series of expressions, but don't have arguments. But there is a Run button.
• Automatic "debugger" sort of thing. When code is executed inside the editor, we automatically show the last value that expression returned inline next to the code.
• Run-as-you-code. If you're coding say a function, you have the option of specifying test / example values for the function arguments. Now that you've specified inputs, we can show intermediate values inline next to the code.

i think this might be related to the "test" question from #3 for the JSON builder

regarding the ideas, i don't think it's necessary to go too deep if it takes too long. the main goal here is just to be able to code the solution to aoc2019 day1. however if we can pull of some of the debugging stuff, it could be a really cool way of solving the problem (how the hell do we see output?) that simultaneously achieves a big improvement in the coding process. that is, making it easier to see what's going on while you're coding. all of the ideas above don't actually seem that hard to implement

[sumeet]

downgrading to 5. i think part of the issue is figuring out what to do. whatever it is we do, i think it won't be hard to implement. i want to do this SOON!

[sumeet]

can see a bit of output after 8ccd0b9, which could look decent a lot of the times

however, the output could look huge, and should be truncated (perhaps using a scrollable child region)

[sumeet]

output's visible now, UI cleanup in #21