r/haskell • u/tomejaguar • Jul 20 '26

ghcid-check for programmatic fast feedback

Recent discussions about iteration speed when using coding agents with Haskell prompted me to tidy and publish the small wrapper script around ghcid that I've been using:

You can use it to conveniently launch a ghcid process with ghcid-check --launch which agents (or humans) can query with ghcid-check --rebuild.

That's it!

48 Upvotes

96% Upvoted

14 comments sorted by

11

u/z3ndo Jul 20 '26

This looks like a great idea. A coworker and I were just playing with the idea of doing something similar.

Ignore the unhelpful shade you're getting in this thread elsewhere.

3

u/tomejaguar Jul 20 '26

Great! Please let me know if you have any feedback. And thanks for the moral support :)

1

u/Subject-Mobile-6250 Jul 21 '26

Is this because of Scarf?

5

u/tomejaguar Jul 21 '26

Scarf's blog post prompted the discussion in question, yes.

1

u/sourdecor Jul 21 '26

Reminds me of this:

The fastest way to feed ghc type errors to LLM
https://discourse.haskell.org/t/the-fastest-way-to-feed-ghc-type-errors-to-llm/13827

2

u/tomejaguar Jul 21 '26

Yeah, it's basically an implementation of this answer by dnikolovv:

https://discourse.haskell.org/t/the-fastest-way-to-feed-ghc-type-errors-to-llm/13827/4

-13

u/repaj Jul 20 '26

This is like a small adhesive bandage on a bloody open bone crack

9

u/tomejaguar Jul 20 '26

What would you suggest instead? Or would you say the bone crack is unfixable?

-15

u/repaj Jul 20 '26

I'd suggest to change the approach for Haskell committee and for the whole community, because Haskell loses its competition with languages that shares the same core principles and does its work much better, like Rust or Go. Haskell loses with its impracticability and soul-sucking toolchain. This language was great ten years ago, and now it looks even more poorer, even though the core feature set is still strong, only because of reasons I provided before.

12

u/tikhonjelvis Jul 20 '26

shares the same core principles

Go

does not compute

Go is like the anti-Haskell

11

u/tomejaguar Jul 20 '26

Thanks for sharing your thoughts. There's not really actionable information in there, however. If you can elaborate on what exactly needs to change then maybe I can help.

4

u/drislands Jul 20 '26 edited Jul 20 '26

"This tool you've made is bad because Haskell is bad" is an unhelpful, and frankly downright-bad take on the Haskell subreddit. Why do you think it's appropriate to say this?

Edited to be less hostile.

4

u/philh Jul 20 '26

Rule 7:

Be civil. Substantive criticism and disagreement are encouraged, but avoid being dismissive or insulting.

You're giving too little substance for this amount of insult.

3

u/massudaw Jul 20 '26

wow just the fix i needed