Conversation

started writing out semantics for my dark hypothesis (that there’s an effect calculus equivalent to lambda calculus but without let or lambdas, where computations are given meaning entirely by effects)

Rob Rix‎

@rob_rix

Apr 3, 2021

it looks like it’s going to be most convenient to express everything structurally rather than nominally. that is, instead of defining an interface for an effect, you just work locally with whatever operations you feel like providing, and so long as they line up with consumers, 👍🏻

Brendan Zabarauskas

@brendanzab

Apr 3, 2021

Will the structural effect operations be labelled?

Replying to

and

Been a bit spooked with the ‘stringy’ nature of the implementations row labels I’ve seen. Seems to pose some issues for modularity? I dunno. 🤔

1:14 AM · Apr 3, 2021Twitter for iPhone

Replying to

yeah, that’s another reason to eschew them. e.g. the capabilities package uses type-level strings for labelled effects, but in fused-effects I went with arbitrary type-level structures, so you can define arbitrary nominal labels and retain modularity.