Frank Alternatives

frank reviews and mentions

• Do Be Do Be Do (2017) [pdf]
  1 project | news.ycombinator.com | 2 Apr 2024

  For the curious, "do be do be do" is a seminal paper in the literature on algebraic effects that introduces _frank_, quirky little language that has algebraic effects but not handlers, at least in the traditional sense.

  Traditionally, an effect handler is an interpreter for a stream of commands, conforming to a specific interface. Generally, handlers surface in languages as a sort of generalized try/catch mechanism, that receive a "callback" to resume the "exception" that produced the command. In frank, not so.

  Frank is based around the idea of _operators_, which generalize functions with the capability of interpreting multiple streams of commands. A plain function can be seen, in fact, as the special case of an operator that interprets no commands.

  Operators are organized around ports and pegs. Pegs are the set of side effects that a computation needs. Each port is an offer to extend that set for downstream callers. Instead of building up a union of effects that each function needs, Frank propogated ambient ability inwards. Operators can then be composed based on the ports and pegs they offer.

  operator: X → [peg]Y

  This works partially because operators are shallow handlers and not deep handlers. Handlers interpret commands: if the handler itself is in scope when interpreting a command, then the language is said to have deep handlers. Frank has shallow handlers, meaning that commands are interpreted in an environment without the handling operator present. Shallow handlers give greater control to the programmer with respect to how commands are interpreted.

  (This is a bad explanation because you already need to know what I'm talking about to understand what I'm talking about, but oh well.)

  My one critism of frank is that the effect model is kinda hard for the working programmer to understand. I can explain Koka effects as "exceptions plus multiple resumption". I don't really have a categorical phrase for frank, and that's its innovation. This isn't so much a criticism but a plea for the pedagogical ramp to this research to improve.

  do be do be do.

  If you're still curious, check out the compiler github repo:

  https://github.com/frank-lang/frank

  And if anything is wrong in the above explanation, please correct me, because we all benefit from Cunningham's Law in the end. Allow me to be the fool.

• Efficient Compilation of Algebraic Effect Handlers - Ningning Xie
  1 project | /r/ProgrammingLanguages | 13 Jul 2022
• Effekt, a research language with effect handlers and lightweight polymorphism
  6 projects | news.ycombinator.com | 19 Nov 2021

  How does this compare to other effect-oriented languages like Koka, Frank, and Eff?

  I've been doing some work with Koka lately, but I briefly looked into the other three (including Effekt) and it mostly came down to, 'Koka seems most active in development'[1] and 'Koka had the easiest to use documentation for me'[2].

  [1] E.g. https://github.com/effekt-lang/effekt had its last commit back in June; https://github.com/frank-lang/frank last commit last year; but https://github.com/koka-lang/koka last update was Oct 15. Effekt seems semi-active, at least, compared to Frank. While stability is good, I wouldn't expect it in a language actively being used for research.

  [2] Comparing https://koka-lang.github.io/koka/doc/book.html and https://effekt-lang.org/docs/ and https://www.eff-lang.org/learn/

• The Problem of Effects (2020)
  5 projects | news.ycombinator.com | 27 Aug 2021
• Extensible Effects in the van Laarhoven Free Monad
  1 project | news.ycombinator.com | 29 Jul 2021
• What are some cool/wierd features of a programming language you know?
  9 projects | /r/ProgrammingLanguages | 12 Apr 2021

  Frank's effect handling. "A strict functional programming language with a bidirectional effect type system designed from the ground up around a novel variant of Plotkin and Pretnar's effect handler abstraction. ... Frank [is different from other PLs with effect type systems in that it is based on] generalising the basic mechanism of functional abstraction itself. A function is simply the special case of a Frank operator that interprets no commands. Moreover, Frank's operators can be multihandlers which simultaneously interpret commands from several sources at once, without disturbing the direct style of functional programming with values. Effect typing in Frank employs a novel form of effect polymorphism which avoid mentioning effect variables in source code. This is achieved by propagating an ambient ability inwards, rather than accumulating unions of potential effects outwards."

• A note from our sponsor - InfluxDB
  www.influxdata.com | 19 Apr 2024

  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. Learn more →