Some thoughts on dependent types

• illacceptanything

  3 1,947 9.4 Ruby

  The project where literally anything* goes.

  

As a next step, let's filter everything from the table with a forall. That's because, when we get a type back from a validator with a forall in it, we have to treat it like a blob because it could be anything. All we know is that it exists, and folks will often call it an existential type. That means we can only pass the blob to functions that accept anything. Some examples are \x -> x (the identity function) and _ -> 5 (a function that returns 5). In our microservice, we're not going to get very far with either of those functions. The table now becomes:

• purescript-vec-dt

  1 5 0.0 PureScript

  Dependently-typed vectors in purescript

That's a lot of prose just to plug a 100-line library I wrote called purescript-vec-dt. I kid, I kid, this was mostly about sharing how I think about dependent types, and incidentally, I wrote a library. Hopefully, what I wrote above makes the library look less magical. Let's look at a bit of application code written with the library.

• InfluxDB

  www.influxdata.com sponsored

  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.

  

Suggest a related project