nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqfcqpp0yd3fw5p6wl9vg3z8xjq7yc5dy5nvv8chvtu944pzu2k5vqlyfy0y (nprofile…fy0y) I wouldn't say they're *totally* irrelevant. But extracting the important pieces of information out of it is a bit of an art that one has to learn, definitely.
I think it's widely agreed that the error message format isn't great, but it's one of those topics where as soon as you're trying to change anything, there's endless bikeshedding.
Despite all this, recent versions of GHC have some improvements.
(1) There's error codes now, and an error message index at https://errors.haskell.org/ where error messages are explained, together with examples and some advice on how to read them.
(2) There's an ongoing move to a more structured error message format *within* GHC, which should make it easier to systematically change the output format via flags or postprocessors etc once this is complete.
Andres Löh /
npub1q8…ymqnn
2024-12-04 10:16:53
in reply to nevent1q…40ht
Author Public Key
npub1q8tuxwdxkr54fv08qrs2yja0e3u0tyju69qje6ht9fldlagre8dqwymqnnPublished at
2024-12-04 10:16:53Event JSON
{
"id": "f21f113e88a1628731251ef392bdc4c798c420fcea297e49f9b5d3a69939188c",
"pubkey": "01d7c339a6b0e954b1e700e0a24bafcc78f5925cd1412ceaeb2a7edff503c9da",
"created_at": 1733307413,
"kind": 1,
"tags": [
[
"p",
"4e0010bc8d8a5d40e9df2b11111cd207898a34949b187c5d8be16b508b8ab518",
"wss://relay.mostr.pub"
],
[
"p",
"0cf3439001f080bb4e3763b1457813119deba500a4f333019fcf284b2fd85faf",
"wss://relay.mostr.pub"
],
[
"e",
"bd867c775eca60c314526593c81f34af4aae7e5ec4b64facef089ab39fbc4693",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://functional.cafe/users/kosmikus/statuses/113594034643893023",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqfcqpp0yd3fw5p6wl9vg3z8xjq7yc5dy5nvv8chvtu944pzu2k5vqlyfy0y I wouldn't say they're *totally* irrelevant. But extracting the important pieces of information out of it is a bit of an art that one has to learn, definitely.\n\nI think it's widely agreed that the error message format isn't great, but it's one of those topics where as soon as you're trying to change anything, there's endless bikeshedding.\n\nDespite all this, recent versions of GHC have some improvements.\n\n(1) There's error codes now, and an error message index at https://errors.haskell.org/ where error messages are explained, together with examples and some advice on how to read them.\n\n(2) There's an ongoing move to a more structured error message format *within* GHC, which should make it easier to systematically change the output format via flags or postprocessors etc once this is complete.",
"sig": "9c3454fef2beb12bd556ad053b9ac9ff2a19e97e72c6f9ffb2c71cce835171f7ae3cd8cb917b537575737b0b1dca84380e5d07740bb54811b3b2707cb5d2860e"
}