Gregory's Server
@wakame @tess @publius @mhoye That sounds like a very dangerous experiment with significant privacy issues.
In highly expressive and/or dynamic languages, it could also be of very limited use.
(But then such dynamic languages usually also have dynamic checks that can tell you *why* the type of something is wrong.)
@lispi314 @tess @publius @mhoye
That's why I introduced it as a thought experiment.
From a usability (or generally practical) perspective:
Of course expressive error messages are (likely) the best solution. With common, handwritten examples perhaps.
And if your interpreter/compiler understands what you are writing, that is always a plus.
But generally it feels as if especially software development is kind of resistant to invent and introduce new tools to make our work easier.
(This post is in danger to walking into "better UI development tools" territory, so I better stop writing now. :blobcatgiggle:)
@lispi314 @tess @publius @mhoye
That's why I introduced it as a thought experiment.
From a usability (or generally practical) perspective:
Of course expressive error messages are (likely) the best solution. With common, handwritten examples perhaps.
And if your interpreter/compiler understands what you are writing, that is always a plus.