2007
DOI: 10.1007/978-3-540-73589-2_2
|View full text |Cite
|
Sign up to set email alerts
|

Gradual Typing for Objects

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
233
0

Year Published

2014
2014
2021
2021

Publication Types

Select...
4
2

Relationship

0
6

Authors

Journals

citations
Cited by 242 publications
(233 citation statements)
references
References 26 publications
0
233
0
Order By: Relevance
“…This is because they imply a more flexible subtyping relationship compared to nominal subtyping, allowing unrelated classes in the class hierarchy to be subtypes. Taking this into account, some type systems [9,22,20] use structural types. In fact, a nominal type also can be considered in terms of its structural representation.…”
Section: Nominal Typesmentioning
confidence: 99%
See 4 more Smart Citations
“…This is because they imply a more flexible subtyping relationship compared to nominal subtyping, allowing unrelated classes in the class hierarchy to be subtypes. Taking this into account, some type systems [9,22,20] use structural types. In fact, a nominal type also can be considered in terms of its structural representation.…”
Section: Nominal Typesmentioning
confidence: 99%
“…With respect to type soundness, Gradualtalk follows the foundational work on gradual typing by Siek and Taha [9], with the blame assignment mechanism of Wadler and Findler [11]. The result is that Gradualtalk guarantees that, if a runtime type error occurs (that is, a MessageNotUnderstood exception is thrown), it is either due to an explicit cast that failed, or the consequence of passing an inappropriate untyped value to typed code.…”
Section: Safety and Type Soundnessmentioning
confidence: 99%
See 3 more Smart Citations