has anyone ever researched/documented the interaction between encoding a large number of effects/dependent-types and API evolution? I'm concerned "usable" forms require lots of inference, which means lots of potential breaking changes to public APIs.
I do think that *in general* spending a lot of time considering how changes will affect your users goes a very long way. If everybody in OSS did this, we would have a lot fewer of these discussions
-
-
There's a lot of value in having a connection with your larger users, and being able to just ask "hey does this commit break your app?". Crater is nice, but ultimately the real breakage is from the servos of the world, and apps of that size are rarely open source.
-
radical reinvisioning of gpl where we make it intractable to be closed source because we will break you if we can't automatically see and update your code for you
- 3 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.