|over 1 year ago||about 1 year ago|
|BSD 2-clause "Simplified" License||-|
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
We haven't tracked posts mentioning polysemy-optics yet.
Tracking mentions began in Dec 2020.
Tying lenses by their focuses
4 projects | /r/haskell | 1 May 2022
It’s worth pointing out there are a few different ways to represent optics. The main ideas you’re playing around with would probably be cleared up by digging into category theory a bit as when you start to understand it it will click. Optics are a concrete implementation that you can use immediately as getters and setters without much background but there potential really lies in their categorical underpinnings that when used properly you can do some very interesting things like allowing local actions to pull back and be ran in a composed global state. Composition is tricky with our implementations though. https://github.com/kvwatkins/Kinds/blob/main/Kinds.Optics.Concrete/Concrete.fs this is your concrete composition for your optics (in fhsharp) you’ll notice the weird affineish optic in there that you don’t normally see that’s what will allow mixed concrete optics to compose cleanly. Profunctor optics are another representation if you dig into will clear things up. https://github.com/hablapps/DontFearTheProfunctorOptics/blob/master/Optics.md is a great read they have more flexible composition which is both a good and bad thing and is still debated. But understanding them and the notions of profunctor a in general applied to a domain will align your current natural intuition with the under pinnings.4 projects | /r/haskell | 1 May 2022
Profunctor optics and the journey to learn the differences between the representations will clear things up. https://github.com/hablapps/DontFearTheProfunctorOptics/blob/master/Optics.md is a great read. The Profunctor have more flexible composition which is both a good and bad thing and is still debated. But understanding them and the notions of Profunctors generally applied to a domain will align your current natural intuition.
What are some alternatives?
vitrea - Optics via the profunctor representation theorem
lens-errors - Handling errors which occur deep inside lens-chains
generic-records - Generically derive traversals, lenses, and prisms.
Kinds - Extending F#'s Capabilities Through Various Means
giphy-api - Giphy HTTP API Wrapper for Haskell
microlens - A lightweight (but compatible with ‘lens’) lenses library