Don Syme explains the downsides of type classes and the technical and philosophical reasons for not implementing them in F#

This page summarizes the projects mentioned and recommended in the original post on /r/haskell

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
  • fslang-suggestions

    The place to make suggestions, discuss and vote on F# language and core library features

  • FSharpPlus

    Extensions for F#

  • There maybe be a way to make it not have overhead. But there is precedent that this is not the case with Statically Resolved Type Parameters, and existing mechanism in F# that already lets you encode Haskell-style typeclasses and is the backbone of FSharpPlus, a typelevel (and more) library for F#. Solving constraints like this at compile-time (as opposed to having a runtime natively understand them) absolutely, positively leads to explosive compile times if you're not careful. I worked on the F# compiler for 5 years and I can attest to numerous reports related to accidental compile-time explosions just because SRTPs or inline was used a particular way.

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
  • FStar

    A Proof-oriented Programming Language

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts