One of my goals for #mollytime is to avoid introducing a concept of errors into the language.
-
@rygorous @aeva which is at odds with the design goal of decreasing the levenshtein distance to making a meaningful change to the program.
i guess it boils down to: what's the worst harm a typo can do in your language?
funny then to consider the shell which has no types and permits casual mistakes of devastating proportions.
-
@morten_skaaning @rygorous @aeva isn't that a big part of every compiler?
-
@morten_skaaning @rygorous @aeva isn't that a big part of every compiler?
-
@morten_skaaning @lritter @rygorous can you check if it halts while you're at it?
-
@morten_skaaning @lritter @rygorous can you check if it halts while you're at it?
@aeva @morten_skaaning @lritter The Halting Problem is oversold.
1. It's not actually generally hard to prove whether any particular invocation will halt. (Just hard to give a single approach that works on everything.)
2. The HP is not even theoretically hard if you expand the set of valid answers to be { yes, no, not sure }
3. practically speaking, the answer is always yes because at some point there will be a sufficiently long power outage or, more likely, forced OS update -
@rygorous @aeva which is at odds with the design goal of decreasing the levenshtein distance to making a meaningful change to the program.
i guess it boils down to: what's the worst harm a typo can do in your language?
funny then to consider the shell which has no types and permits casual mistakes of devastating proportions.
-
@JamesWidman @lritter @rygorous that'll definitely save me from accidentally transposing the source and destination paths on various commands to exciting effect
-
@JamesWidman @lritter @rygorous that'll definitely save me from accidentally transposing the source and destination paths on various commands to exciting effect
@aeva @JamesWidman @lritter see, if this was typesafe with proper constructors that could not happen:
cp(ThisIsTheSourcePath("foo"), ThisIsTheDestinationPath("bar"));
-
@lritter I do like C++ for being something that strikes an ok-ish balance between making me stop and think, and letting me iterate quickly.
@aeva @lritter I actually like GDscript's typing for the same reason. I like having static typing so I get editor hints and can make sure I don't mess something up. But I can also tell it to just not do that and it's cool with that.
As opposed to python where you can set your string to 3 and the solution is just to make sure you don't do that.
-
@aeva @lritter I actually like GDscript's typing for the same reason. I like having static typing so I get editor hints and can make sure I don't mess something up. But I can also tell it to just not do that and it's cool with that.
As opposed to python where you can set your string to 3 and the solution is just to make sure you don't do that.