Conversation

I’ve said it before:

Quote Tweet

· Aug 4, 2021

Replying to @http406

Even if it’s a situation where the compiler can’t go on, is it really an error if that’s normal/expected? I’m a Haskell “expert” and still surprised when anything but the most trivial program compiles on the first go. Almost all of my compiles end in “errors”, on purpose.

In multiple ways:

Quote Tweet

· Aug 3, 2021

Thinking of type “errors”—or even syntactic “errors”—comes pre-burdened for free with a really unfortunate set of assumptions and hostile framing. Your program is *wrong*! It’s got an *unexpected* mismatch between this and that. You need to *fix* it before I’ll *let* you proceed.

Show this thread

With concrete advice:

Quote Tweet

· Aug 21, 2020

Adopting this attitude (ca. 2012 iirc) changed the whole way I do language design and tooling development. Compiler/interpreter error messages are the single best place to surface learning materials for a language, because trial *and error* is a huge aspect of how people learn! twitter.com/ManishEarth/st…

Show this thread

I will continue to say this until we make the computer quit being mean. It’s an important realisation that the process of figuring out how to get your code to compile is programming too, and it shouldn’t be a realisation at all—it should be clear from the user interface design.

Esteban K�ber –

@ekuber

You know what? I make an effort to always use plain language and try to come accross as matter of fact (playfulness might be accepted but is frowned upon) in diagnostics, but just removing the leading "error:" might actually be a small change ti reframe the interaction.

Exactly! Doing that has led me in a direction I like, at least. Including a “warning” or “error” prefix does serve some purposes, like helping IDEs/editors format messages that follow (or vaguely imitate) the standardish GNU format, although those tags aren’t very informative.

“Error” might be “I can’t”, or “You’ve asked me not to”, or “I will, but only if you super-promise that these shenanigans are what you meant to do”; “warning” might be about anything: style, performance, possible issues, or even *likely* issues too noisy to make errors.

Brendan Zabarauskas

@brendanzab

11:46 AM · Oct 9, 2021Twitter Web App

Any idea what a better prefix would be? Or would it be better to just remove it? Or do we dial down the severity of this stuff in development, so you get 'info' and 'note' messages instead, leaving the errors for CI and release builds?

Replying to

and

(this doesn't solve the issues you raised in the previous tweet, just wondering as somebody who makes a diagnostic reporting library, hehe 😳)

Replying to

and

If you can break with convention, removing `error: ` is an easy win

Brendan Zabarauskas

@brendanzab