Thanks for the explanation (about stack.yaml)... yes, that's what I understood. This behaviour makes sense once I understood why those files are here, but I had to dig deep in stack documentation to understand that.
To me, the issue here is that as a begginer, I must learn how Stack resolves dependencies, and how it is managing multiple packages repositories in order to understand what I should do to install a simple dependency.... that is quite useless, and frankly quite a lot to learn, when just trying to write 30 lines of Haskell in a toy project.
As awsome and sensible as Stack might be, I think it should have a "degraded" behaviour, sensible defaults that do not leak those advanced use cases on simple projects, thus matching other package managers behaviours...
As for the documentation thing, I think that detailed tutorials are a bit overkill, but showing at least a few snippets of the most common or most simple use cases is quite enjoyable to understand what a lib does, and where to start when trying to understand it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
FYI there are quite a few more comments on reddit 😊
Thanks for the explanation (about stack.yaml)... yes, that's what I understood. This behaviour makes sense once I understood why those files are here, but I had to dig deep in stack documentation to understand that.
To me, the issue here is that as a begginer, I must learn how Stack resolves dependencies, and how it is managing multiple packages repositories in order to understand what I should do to install a simple dependency.... that is quite useless, and frankly quite a lot to learn, when just trying to write 30 lines of Haskell in a toy project.
As awsome and sensible as Stack might be, I think it should have a "degraded" behaviour, sensible defaults that do not leak those advanced use cases on simple projects, thus matching other package managers behaviours...
As for the documentation thing, I think that detailed tutorials are a bit overkill, but showing at least a few snippets of the most common or most simple use cases is quite enjoyable to understand what a lib does, and where to start when trying to understand it.