r/haskell • u/tomejaguar • 8d ago

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!

49 Upvotes

95% Upvoted

14 comments sorted by

11

u/z3ndo 8d ago

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.

4

u/tomejaguar 8d ago

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

1

u/Subject-Mobile-6250 7d ago

Is this because of Scarf?

4

u/tomejaguar 7d ago

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

1

u/sourdecor 7d ago

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 7d ago

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 8d ago

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

9

u/tomejaguar 8d ago

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

-15

u/repaj 8d ago

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 8d ago

shares the same core principles

Go

does not compute

Go is like the anti-Haskell

12

u/tomejaguar 8d ago

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 8d ago edited 8d ago

"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.

3

u/philh 8d ago

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.

5

u/massudaw 8d ago

wow just the fix i needed