hirrolot

(* The syntax of our calculus. Notice that types are represented in the same way
   as terms, which is the essence of CoC. *)
type term =
  | Var of string
  | Appl of term * term
  | Binder of binder * string * term * term
  | Star
  | Box

and binder = Lam | Pi

iacchus

#!/usr/bin/env sh

# Original author: Michalis Georgiou <[email protected]>
# Modified by Andrew http://www.webupd8.org <[email protected]>
# Current version by Kassius Iacchus https://github.com/iacchus/

# Depends on: `wget`
#
# Install `wget` on Debian/Ubuntu with:
# apt install wget

Diggsey

Looking into the Future

futures-rs is the library which will hopefully become a shared foundation for everything async in Rust. However it's already become renowned for having a steep learning curve, even for experienced Rustaceans.

I think one of the best ways to get comfortable with using a library is to look at how it works internally: often API design can seem bizarre or impenetrable and it's only when you put yourself in the shoes of the library author that you can really understand why it was designed that way.

In this post I'll try to put down on "paper" my understanding of how futures work and I'll aim to do it in a visual way. I'm going to assume you're already somewhat familiar with Rust and why futures are a useful tool to have at one's disposal.

For most of this post I'll be talking about how things work today (as of September 2017). At the end I'll touch on what's being proposed next and also make a case for some of the changes I'd like to see.

If you're interested in learning more ab

mcomisso

import requests, json

#Commont utils url and authToken
authToken = ""
baseLikeUrl = "https://api.gotinder.com/like/"
baseProfileUrl = "https://api.gotinder.com/user/"
myFeed = "https://api.gotinder.com/user/recs"


s = requests.Session()