Skip to content
0:00 / 0:00

#haskell#dependenttypes

Dependently Typed Haskell in Industry (Experience Report)

ACM SIGPLAN

11K subscribers • 61 videos on Hallway

YouTube
  • Recommended by 1 person: 1 in engineering communities.

Intermediate. Assumes working knowledge.

2.4K views6 years ago1 recommendation

Programming languagesTools and practiceFunctional programmingComputation and complexity

An experience report on using dependently typed Haskell in industrial software development.

The uploader added no description.

Why it's here

1 person recommends this

What people say. Recommended as a practical experience report on using dependent types in production Haskell.

Moments people linked to

u/Faucelmein r/haskell • Recommends

Dependently Typed Haskell in Industry (Experience Report)

u/Faucelmein r/haskell • Mentions

On “Eliminating Bugs with Dependent Haskell - Experience at Facebook (Noam Zilberstein)”

There's also Dependently Typed Haskell in Industry (Experience Report). link to this video.

u/runeksin r/haskell • Mentions

On “Dependently Typed Haskell in Industry (Experience Report)”

17:39 Philip Wadler asks a question
3View on Reddit

u/davidchristiansenin r/haskell • Mentions

On “Systems engineer at SimpleX Chat”

My experience is also that writing the boilerplate manually is not so onerous. I used to work with parameterized-utils a lot - a nice thing about it is that the datatypes in it have been used in a real performance-sensitive code base in the past. A challenge of programming with lots of fancy types in Haskell is that you end up writing a lot of what amount to overly-strict identity functions, e.g. to reindex some indexed datatype. This breaks sharing unnecessarily. Also, efficient datatypes don't always lend themselves to a convenient type-level computation of the indices. The library provides versions of these operators that are just unsafeCoerce under the hood, and the real non-cheating ver…