Brendan Zabarauskas on Twitter: "@evincarofautumn @typeswitch Yeah I like the idea of constraints here. I also wonder if it these could be seen as some sort of 'co-effect'? Ie. a restriction on the contexts where stuff can be invoked? Not sure if that would be annoying in practice though." / Twitter

This Tweet was deleted by the Tweet author. Learn more

Dec 21, 2020

Explicitly supporting platform-specific code is good. How to define “platform” is important—build/host/target+CPU+OS+…? I generally want to choose from a short list of coarse-grained supported platforms (arch+OS) or depend on fine-grained platform features (OS APIs, CPU insns).

1

2

Jon Purdy

@evincarofautumn

Dec 21, 2020

I want to do the latter in Kitten—platform constraints as constraints on functions—partly because it’s more flexible, partly so that it’s more of a first-class thing in the type system, but tbh largely because I don’t know where to draw lines—posix, linux, gnu/linux, ubuntu…?

2

Replying to

and

Yeah I like the idea of constraints here. I also wonder if it these could be seen as some sort of 'co-effect'? Ie. a restriction on the contexts where stuff can be invoked? Not sure if that would be annoying in practice though.

5:18 AM · Dec 21, 2020Twitter Web App

1

Like

Conversation