Blogged: Haskell's kind system - a primer!
https://t.co/9eG8kX4Ict
Big shout-out to @mattoflambda, @_shrynx, Fintan and Miguel Esteves for helping me review this post! #haskell#fp
@Lfromthenorth@mattxiv@AnaKasparian But terms like "menstruating person" aren't used refer to women. They're used to refer to people who menstruate, of which women are a part of.
How is using accurate terms to refer to a specific subset of the population dehumanizing?
@Lfromthenorth@mattxiv@AnaKasparian Talking to a specific person (which is what you're talking about) is not the same as referring to a subset of the population with certain characteristics (which is what @mattxiv is talking about).
No one is arguing you should refer to a specific person as "Ms Birthing Person".
@kerckhove_ts@spencerjanssen Using the raw functions from tz alone, it's easy to get things wrong. See the motivation section in the Readme
https://t.co/7RrBAgJ3sJ
@kerckhove_ts@spencerjanssen Yup, that's what tztime uses under the hood.
The problem tztime aims to solve is the complications you quickly run into when manipulating time (adding time, subtracting time, getting the time at the start of day, etc).
@kerckhove_ts@spencerjanssen Not if you use the intended constructor functions (see Screenshot)
You're not supposed to use the TZInfo constructor. Maybe I should have hidden it behind an "Internal" module 😅
@kerckhove_ts@spencerjanssen Might I also throw my own package in the ring? https://t.co/kJ7pMhY3pm
It's built on top of the tz/tzdata packages, (IMO) improved ergonomics, hard to misuse.
In our latest article, @int_index tries to solve a long-standing misconception about how the DataKinds extension works.
Read on our blog: https://t.co/Y3YNvScDNq