After extensively using the #lens#Haskell library for half a year at work I have now played around with the #optics library again. I am amazed by how much more helpful error messages are with #optics. It’s an amazing library and I would recommend it over #lens whenever you have the choice.
@mangoiv I do not know what you mean. You need to depend on optics-core to provide lenses usable with the library, just because the type of those optics is not a type alias like it is in lens.
@maralorn yuh I just mean like often, when you have a heavy type directed eDSL, they’re optimised for a specific purpose. That means it adds a significant amount of churn if you want to do anything yourself. One example of that is polysemy. Another one is squeal-postgresql
@mangoiv Hasn’t been my impression with #optics yet. To me it feels like the type level stuff is "finished". As long as you only define and use existing types of optics you don’t need to worry about it.
Add comment