On Friday October 17, this site was moved to a new server, https://mw.hh.se. The original address will continue to work. Whithin a week or two this site will return to the original address. /Peo HH IT-dep
WG211/M15Igarashi: Difference between revisions
From WG 2.11
Jump to navigationJump to search
Created page with "Type systems for a polymorphic imperative multi-stage language It is well known that naive combination of let-polymorphism with mutable references makes an unsound type system. ..." |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
Type systems for a polymorphic imperative multi-stage language | ''Type systems for a polymorphic imperative multi-stage language'' by Atsushi Igarashi | ||
It is well known that naive combination of let-polymorphism with | It is well known that naive combination of let-polymorphism with | ||
mutable references makes an unsound type system. The problem is | mutable references makes an unsound type system. The problem is | ||
even more subtle in | even more subtle in MetaOCaml-like multi-stage languages; indeed, | ||
Kiselyov and Shan have discovered, naive value restriction does | as Kiselyov and Shan have discovered, naive value restriction does | ||
not work. In this talk, I'll discuss two type systems to deal | not work. In this talk, I'll discuss two type systems to deal | ||
with this problem. | with this problem. | ||
Joint work with Megumi Kobayashi. | Joint work with Megumi Kobayashi. | ||
Latest revision as of 14:19, 28 October 2015
Type systems for a polymorphic imperative multi-stage language by Atsushi Igarashi
It is well known that naive combination of let-polymorphism with mutable references makes an unsound type system. The problem is even more subtle in MetaOCaml-like multi-stage languages; indeed, as Kiselyov and Shan have discovered, naive value restriction does not work. In this talk, I'll discuss two type systems to deal with this problem.
Joint work with Megumi Kobayashi.
