On Sun, Jul 20, 2014 at 8:00 PM, Jonathan S. Shapiro <[email protected]> wrote:

> This can be viewed as type, or it can be viewed as a known constraint on a
> value of some type. How do we want to think about this case?

so it came to mind that 'typestate' is much like a constraint on a
value of some type,
and that rust had/removed typestate, after a little looking into it,
it seems they replaced it with 'viewed as a type', in the form of
phantom types with a private constructor...

It seems different enough issues (with type mutation and all that)...
and I still don't really see exactly a way to make 'as a type' work
nicely with inference,
but at least typestate can force the constraints into the caller...

http://pcwalton.github.io/blog/2012/12/26/typestate-is-dead/

so its not exactly uncharted waters I suppose.
_______________________________________________
bitc-dev mailing list
[email protected]
http://www.coyotos.org/mailman/listinfo/bitc-dev

Reply via email to