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

Ellen Arvidsson

dblp:356/3634 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
1since 2021 · last 2023
0009-0004-0878-3641ORCID · reported

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

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

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
1 paper
Programming languages and type systems · 77% Operating systems · 23%

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

TopicWeightPapersLastEvidence papers
Programming languages and type systems › type systems
ownership types
0.712023
Reference Capabilities for Flexible Memory Management · Proc. ACM Program. Lang. 2023
Programming languages and type systems
type systems
0.712023
Reference Capabilities for Flexible Memory Management · Proc. ACM Program. Lang. 2023
Operating systems › resource management
memory management
0.212023
Reference Capabilities for Flexible Memory Management · Proc. ACM Program. Lang. 2023
Operating systems › resource management › memory management
region-based memory management
0.212023
Reference Capabilities for Flexible Memory Management · Proc. ACM Program. Lang. 2023

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

region isolation · 0.7ownership type system · 0.7
YearPublicationVenuePosition
2023 Reference Capabilities for Flexible Memory Management
abstract
Verona is a concurrent object-oriented programming language that organises all the objects in a program into a forest of isolated regions. Memory is managed locally for each region, so programmers can control a program's memory use by adjusting objects' partition into regions, and by setting each region's memory management strategy. A thread can only mutate (allocate, deallocate) objects within one active region---its "window of mutability". Memory management costs are localised to the active region, ensuring overheads can be predicted and controlled. Moving the mutability window between regions is explicit, so code can be executed wherever it is required, yet programs remain in control of memory use. An ownership type system based on reference capabilities enforces region isolation, controlling aliasing within and between regions, yet supporting objects moving between regions and threads. Data accesses never need expensive atomic operations, and are always thread-safe.
Ellen Arvidsson, Elias Castegren, Sylvan Clebsch, Sophia Drossopoulou, James Noble 0001, Matthew J. Parkinson, Tobias Wrigstad
Proc. ACM Program. Lang.1