microsoft/verona

Research programming language for concurrent ownership

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 50 minutes ago
Added to GitGenius on September 18th, 2026
Created on September 14th, 2019
Open Issues & Pull Requests: 15 (+0)
GitHub issues: Enabled
Number of forks: 173
Total Stargazers: 3,726 (+0)
Total Subscribers: 102 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 704.3 days
Mean response time: 704.3 days
90th percentile: 704.3 days
Tracked items: 1

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 764 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Language Spec (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Verona is a research programming language designed to explore concurrent ownership as a new concurrency model.

The project addresses the challenge of safely managing concurrent access to shared resources by integrating ownership semantics directly into the language design. Rather than relying on traditional locking mechanisms or garbage collection, Verona's approach weaves ownership rules into the type system, allowing the compiler to reason about which parts of a program can safely access data concurrently. This enables developers to write concurrent code with stronger guarantees about data safety without runtime overhead.

Verona is explicitly positioned as a research project in early stages and is not ready for production use outside academic contexts. It is undergoing significant refactoring, which means the codebase and APIs are unstable. The tool is most appropriate for researchers exploring concurrent ownership models, language designers studying type-system approaches to concurrency, and academic collaborators interested in contributing to the project's evolution. This is not suitable for building production systems or applications that require stability.

The project shows active development with ongoing architectural changes. Work is concentrated on core language and compiler infrastructure rather than breadth of features. The codebase reflects experimental research priorities, with substantial portions being rewritten as the design matures.