TTC Feedback

The release of TTC 1.0.0.0 went well, and I received a fair amount of feedback on the Haskell-Cafe announcement thread and Haskell Reddit announcement post. The project was first released in late 2019, but this was the first general announcement, and it is the first time for me to receive feedback on the project!

Based on the feedback, there are two major changes that I am considering. Both are design decisions that I have considered since the very beginning of the project, and it is great to have feedback from others about them. I have created a GitHub issue for each possible change.

• Orphan instances for core types
• Text Builder, ByteString Builder, ShortByteString support in Textual

I purposefully wrote those issues without editorializing them. After sleeping on it last night, I have pretty firm opinions on both, but I will of course consider any opinions and preferences expressed. Unless there is a reason to wait longer, I would like to make a decision and proceed on Monday. If there are breaking changes, it is best to make them soon, while there are few users of the library.

I learned about a “design pattern” that is new to me from Miguel Mitrofanov, which I may use in TTC. I am thinking about writing an article about it as well.

I was also informed of many projects to add to the related work section of the README. Taylor Fausak, the host of the Haskell Weekly Podcast, told me about his general conversion library, witch, and asked what I think about it. It is very well done, and I will likely use it in the future. Reading through the code, I found one thing that I plan on implementing in TTC right away: the use of HasCallStack on unsafe functions to get more useful error messages when they fail.

Also on my task list, I plan on making some updates and adding some more information to the project README based on feedback.