Coroutines and Effects

• capslock

  2 581 8.7 Go
  

Wow I’ve been thinking of something exactly like this! Sort of a super charged, statically typed version of Go’s context.Context. It would allow you to describe the capabilities (or effects) of every function, including IO, memory allocation, cancellation, deadlines, concurrency, and whatever application-specific stuff you need on there (like logging).

Then you could implement something like Google [0] just by looking at type signatures.

0. https://github.com/google/capslock

• kyo

  5 422 9.9 Scala

  Toolkit for Scala Development

  

Indeed - I do not think it is a coincidence that a lot of production experiments in effect systems are happening in Scala right now - the language is very flexible to conduct them. https://github.com/getkyo/kyo in particular looks interesting as it explores a different space where the monadic nature is less exposed to the end user.

• InfluxDB

  www.influxdata.com featured

  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.

  

• 30-seconds-of-interviews

  1 11,903 - JavaScript

  Discontinued A curated collection of common interview questions to help you prepare for your next interview. (by Chalarangelo)

https://github.com/Chalarangelo/30-seconds-of-interviews/blo...

Exception handling, for example, uses dynamic scoping since you don't know what will be handling your exception when you write code which throws it.

Another way of thinking about it is, with dynamic scoping the value of the dynamic variable must always be on the stack and the closest one is the value that will be used. This is a really good behaviour for global variables since a common source of bugs is some global variables (and I'm considering class members "global" for this) getting changed unexpectedly. If the variable is lexical then it can be very hard to figure out what changed the value (especially when threads are involved) but if the variable is dynamic it's easy: the culprit is on the stack.

Suggest a related project