The Lisp variant that the compiler supports at the moment only handles f64 numbers so I don't think this kind of issue is possible.
However, this is a very relevant point. If the goal is just shorter code (as opposed to a mix of shorter code and less run-time operations), then you need to check that folding strings (and similar types) actually makes the expression shorter to represent.
When a val is deployed on val town, my understanding is that it's parsed/compiled. At that point, can you save the parts of the program that people might search for? Names of imports, functions, variables, comments, etc.
As long as you don’t care about unit test ability. Usually if you bothered to write them in Python or JS you usually don’t want to regress back to shell stuff. You’re already in a place where you have a runtime available so you can do way more stuff.
It’s usually the opposite direction that you mentioned that you want to go. You one liner some shell like awk to quickly get shit done without worrying about a runtime being available to you and then if you need it to be more robust and legible because of testing etc or production grade you move to a proper dynamic scripting environment
I'm really happy with the way val town responded to the security issues I raised! Big congrats to them for shipping this change – it sounds tricky on both the product and the tech side of things.
If by auto-repost you mean when we email someone inviting them to repost a story, it's exactly the same thing as the second-chance pool except for a technical difference: if the submission is less than 2-3 days old, we re-up it; if it's older than that, we email a repost invite.
Thanks! I always assumed there was a bigger difference between "you mail me" and "you simple repost", but it makes sense that the time elapsed is a factor.
