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

Aleks Bromfield

dblp:81/7473 · DBLP profile ↗
← Back
2ranked-venue papers
0as first author
0since 2021 · last 2012
—ORCID · none

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

Software engineering, systems software and programming languages · 2

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 · 75% Concurrent programming · 25%

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

TopicWeightPapersLastEvidence papers
Concurrent programming › concurrency bugs
data race freedom
0.112012
Uniqueness and reference immutability for safe parallelism · OOPSLA 2012
Concurrent programming › concurrency correctness
safe parallelism
0.112012
Uniqueness and reference immutability for safe parallelism · OOPSLA 2012
Programming languages and type systems › type systems
soundness
0.112012
Uniqueness and reference immutability for safe parallelism · OOPSLA 2012
Programming languages and type systems › type systems › refinement types
type qualifiers
0.112012
Uniqueness and reference immutability for safe parallelism · OOPSLA 2012
Programming languages and type systems
type systems
0.112012
Uniqueness and reference immutability for safe parallelism · OOPSLA 2012
Programming languages and type systems › type systems › substructural type systems
uniqueness and immutability
0.112012
Uniqueness and reference immutability for safe parallelism · OOPSLA 2012
Programming languages and type systems
language design
0.112009
Flapjax: a programming language for Ajax applications · OOPSLA 2009
Programming languages and type systems › programming paradigms
reactive programming
0.112009
Flapjax: a programming language for Ajax applications · OOPSLA 2009
Programming languages and type systems › domain-specific languages
web programming language
0.112009
Flapjax: a programming language for Ajax applications · OOPSLA 2009

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

dataflow propagation · 0.1
YearPublicationVenuePosition
2012 Uniqueness and reference immutability for safe parallelism
abstract
A key challenge for concurrent programming is that side-effects (memory operations) in one thread can affect the behavior of another thread. In this paper, we present a type system to restrict the updates to memory to prevent these unintended side-effects. We provide a novel combination of immutable and unique (isolated) types that ensures safe parallelism (race freedom and deterministic execution). The type system includes support for polymorphism over type qualifiers, and can easily create cycles of immutable objects. Key to the system's flexibility is the ability to recover immutable or externally unique references after violating uniqueness without any explicit alias tracking. Our type system models a prototype extension to C# that is in active use by a Microsoft team. We describe their experiences building large systems with this extension. We prove the soundness of the type system by an embedding into a program logic.
Colin S. Gordon, Matthew J. Parkinson, Jared Parsons, Aleks Bromfield, Joe Duffy
OOPSLA4
2009 Flapjax: a programming language for Ajax applications
abstract
This paper presents Flapjax, a language designed for contemporary Web applications. These applications communicate with servers and have rich, interactive interfaces. Flapjax provides two key features that simplify writing these applications. First, it provides event streams, a uniform abstraction for communication within a program as well as with external Web services. Second, the language itself is reactive: it automatically tracks data dependencies and propagates updates along those dataflows. This allows developers to write reactive interfaces in a declarative and compositional style.
Leo A. Meyerovich, Arjun Guha, Jacob P. Baskin, Gregory H. Cooper, Michael Greenberg 0002, Aleks Bromfield, Shriram Krishnamurthi
OOPSLA6