typed-racket

Typed Racket

Go to file

Asumu Takikawa 99ebb7e51c Remove the depth subtype check on #:implements This check was not really necessary to begin with, but I thought it might be a useful sanity check. In retrospect, calling `subtype` here causes other headaches (such as when registering type aliases) and is confusing when multiple #:implements are provided. Instead, the #:implements clauses are just linearized and the last type for any given method/field is taken. This may also prevent a heisenbug that occurs in the GUI framework types. I still don't know the root cause of that non-determinism though. Closes PR 14669 original commit: 9b4e3befa3605851f1ee30f20f4a38edd06dd8a9	2014-11-20 12:20:28 -05:00
pkgs/typed-racket-pkgs	Remove the depth subtype check on #:implements	2014-11-20 12:20:28 -05:00

Asumu Takikawa 99ebb7e51c Remove the depth subtype check on #:implements

This check was not really necessary to begin with,
but I thought it might be a useful sanity check. In
retrospect, calling `subtype` here causes other headaches
(such as when registering type aliases) and is confusing
when multiple #:implements are provided.

Instead, the #:implements clauses are just linearized
and the last type for any given method/field is taken.

This may also prevent a heisenbug that occurs in the
GUI framework types. I still don't know the root cause of
that non-determinism though.

Closes PR 14669

original commit: 9b4e3befa3605851f1ee30f20f4a38edd06dd8a9

2014-11-20 12:20:28 -05:00

pkgs/typed-racket-pkgs

Remove the depth subtype check on #:implements

2014-11-20 12:20:28 -05:00