Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Matthew S. Tschantz

dblp:82/1623 · DBLP profile ↗
← Back
4ranked-venue papers
1as first author
0since 2021 · last 2008
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 4 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
2 papers
Programming languages and type systems · 81% Software maintenance and evolution · 19%

Topics — the 5 heaviest of 6, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Programming languages and type systems › type systems › alias typing
reference immutability
0.112005
Javari: adding reference immutability to Java · OOPSLA 2005
Programming languages and type systems
type systems
0.112005
Javari: adding reference immutability to Java · OOPSLA 2005
Programming languages and type systems › type systems › polymorphism
generics
0.012004
Converting java programs to use generic libraries · OOPSLA 2004
Software maintenance and evolution › software reengineering › software modernization › software migration
legacy system migration
0.012004
Converting java programs to use generic libraries · OOPSLA 2004
Programming languages and type systems › type systems › polymorphism
parametric polymorphism
0.012004
Converting java programs to use generic libraries · OOPSLA 2004

Methods — techniques the papers use, named apart from their topics

type soundness proof · 0.1type inference · 0.0
YearPublicationVenuePosition
2008 Inference of Reference Immutability
Jaime Quinonez, Matthew S. Tschantz, Michael D. Ernst
ECOOP2
2007 The Daikon system for dynamic detection of likely invariants
Michael D. Ernst, Jeff H. Perkins, Philip J. Guo, Stephen McCamant, Carlos Pacheco, Matthew S. Tschantz, Chen Xiao
Sci. Comput. Program.6
2005 Javari: adding reference immutability to Java
abstract
This paper describes a type system that is capable of expressing and enforcing immutability constraints. The specific constraint expressed is that the abstract state of the object to which an immutable reference refers cannot be modified using that reference. The abstract state is (part of) the transitively reachable state: that is, the state of the object and all state reachable from it by following references. The type system permits explicitly excluding fields from the abstract state of an object. For a statically type-safe language, the type system guarantees reference immutability. If the language is extended with immutability downcasts, then run-time checks enforce the reference immutability constraints.This research builds upon previous research in language support for reference immutability. Improvements that are new in this paper include distinguishing the notions of assignability and mutability; integration with Java 5's generic types and with multi-dimensional arrays; a mutability polymorphism approach to avoiding code duplication; type-safe support for reflection and serialization; and formal type rules and type soundness proof for a core calculus. Furthermore, it retains the valuable features of the previous dialect, including usability by humans (as evidenced by experience with 160,000 lines of Javari code) and interoperability with Java and existing JVMs.
Matthew S. Tschantz, Michael D. Ernst
OOPSLA1
2004 Converting java programs to use generic libraries
abstract
Java 1.5 will include a type system (called JSR-14) that supports parametric polymorphism, or generic classes. This will bring many benefits to Java programmers, not least because current Java practice makes heavy use of logically-generic classes, including container classes.
Alan Donovan, Adam Kiezun, Matthew S. Tschantz, Michael D. Ernst
OOPSLA3