Hylo’s implementation is at a very early stage. Key components of the compiler are still to be implemented before a first version of the language can be used. Further, some aspects of the language design are still immature and will likely require more iterations.

This page gives an overview of our roadmap going forward and provides details on our main milestones.

2023 - Q1/Q2

While we weren’t able to deliver an alpha version of Hylo in 2022, we made significant progress on our original goals. In particular, we finalized the design of stored projections, a feature essential to implement collection views of generic types in safe Hylo. Elements of our design are presented here: https://github.com/hylo-lang/hylo-lang.github.io/discussions/39.

Our main objectives for the first half of 2023 are now as follow:

• deliver an alpha version of Hylo;
• validate the language’s design; and
• assess its usability.

Progress toward those objectives will be measured by the following milestones:

Implement a reference compiler

We expect to deliver a first version of an experimental compiler for Hylo sometime in late Q2. This implementation will serve as a proof of concept to build non-trivial programs and evaluate the language’s usability. As such, we will not focus on performance and will push most optimizing code transformations to 2024.

We have already built a prototype capable of compiling a small subset of Hylo to LLVM. The following key components must be either completed or developed from scratch to turn that prototype into a working implementation:

Type inferrer/checker

The type inferrer/checker is the component responsible to verify that programs satisfy the flow-insensitive semantics of Hylo. Its current implementation can analyze a sizeable subset of Hylo. However, significant effort is still required to support generic features.

Intermediate representation

Once checked by the flow-insensitive type checker, Hylo programs are translated to an intermediate representation (IR) that is used to perform flow-sensitive type checking (a.k.a. lifetime and ownership analysis) and guaranteed optimizations.

Although we have already laid out foundations, the design of the IR itself is still a work in progress, as it is being co-designed with its implementation. We plan on providing a specification by the end of the year.

The translation from Hylo source to the IR currently handles a small subset of the language.

Lifetime and ownership analysis

Lifetime and ownership analysis are two transformation passes that consume raw IR, freshly translated from the source code. They instrument it with appropriate instructions to model the state of objects and memory at runtime and finally check whether programs satisfy the flow-sensitive semantics of Hylo.

The current implementation handles the same small subset as the IR translation.

LLVM Code generation

We opted to use LLVM as our backend. Thus, the last step of our frontend pipeline is to emit bitcode and let LLVM generate machine code.

2023 - Q3/Q4

Our main objectives for the second half of 2023 will be to:

• complete the design of our language;
• implement a standard library; and
• write and publish a specification.

Progress toward those objectives will be measured by the following milestones:

Complete the language design

Though many of the core principles of Hylo’s design have been established already, there are still important open questions to address. We consider the answers to these questions essential to the development of a viable alpha version of the language.

Concurrency

The design of Hylo’s concurrency is still immature. Though we have laid out some key principles, important questions have yet to be answered:

• Should we support concurrent interprocess communication?

Interprocess communication is a thorny problem in a programming language advocating for mutable value semantics. The core issue is that a communication channel is essentially a mutable reference.

Our current position is that safe Hylo should not compromise on its strict adherence to value semantics, de facto discarding all forms of communication except at spawn and join events. Nonetheless, we plan on investigating whether such a restriction is acceptable by developing a collection of concurrent program examples.

• Should we support cancellation at the language level?

Though it might be possible to implement cancellation at the library level with a handful of carefully written types that wrap unsafe operations behind safe APIs, proper language support may be required for the sake of usability and/or performance.

Implement a standard library

Once we will have delivered the experimental compiler, A good part of Q4 will be dedicated to the implementation of a standard library for the language. We will base our design on Swift’s standard library, for two reasons:

1. Swift has had time to empirically demonstrate the success of its approach to generic programming; and
2. Hylo and Swift share very similar type systems, so we expect the concepts developed in the latter to be portable in the former.

Write and publish the specification

A complete specification of the language will increase confidence in the soundness of the language design. It will also serve as a reference document to write the implementation.

The specification is currently an ongoing work that we expect to be delivered together with an alpha version of the language implementation. However, sections that relate to the semantics of the language still require significant effort.

We also plan on publishing the specification in the form of a website or GitBook.

2024

Our main objectives for 2024 will be to

• develop the missing features of the language;
• investigate optimal implementation strategies implement an efficient compiler;
• implement two-way interoperability with C++; and
• develop an inclusive community.

Implement guaranteed optimizations

Hylo is designed in such a way that it can communicate runtime costs very transparently. As a result, the language can offer several guaranteed optimization. For example, Hylo guarantees that closures do not require heap allocation unless the type of their environment is erased. We plan on implementing these guaranteed optimizations over Q1 and Q2.

Investigate implementation strategies for concurrency

Once we will have finalized the design of Hylo’s concurrency model, we will be able to investigate the optimal implementation strategies.

We are leaning toward a stackful coroutines, mostly to avoid monadic asynchronous programming (a.k.a. polychromatic functions), where asynchronous operations can only be called from asynchronous contexts. Nonetheless, discussions with experts have revealed that such a strategy may induce unfortunate runtime costs and that stackless coroutines may not necessarily force a monadic asynchronous style upon the language.

One solution might be to adopt a stackful model as a default strategy and surface stack information in the type system to let the compiler opt for stackless code generation whenever possible.

We plan on having adopted and implemented a strategy by the end of Q3.

Design and implement missing language features

Some of the features on our wishlist are out of scope for 2023, as we believe they are not essential to assess the validity of the language’s design. 2024 will allow us to revisit these features with a working experimental implementation.

One of our main goals will be the inclusion of variadic generic parameters. Hylo already supports scalar generic type and value parameters. The former enable bounded polymorphism by the means of type constraints; the latter enable a restricted form of dependent types by allowing types and operations to be parameterized by values computed during compilation. A canonical example is a buffer (i.e., a fixed-size array).

extension Buffer {
  fun concatenate<a: Int>(
    _ other: Buffer<Self.Element, a>
  ) -> Buffer<Self.Element, Self.size + a> { ... }
}

Support for variadic generic parameters will greatly improve Hylo’s expressiveness with respect to type-level metaprogramming. Our work in this area will be informed by contemporary efforts to leverage compile-time evaluation for metaprogramming, such as Circle.

Other notable features in our wishlist include:

• exception handling;
• polymorphic effects; and
• resumable functions (a.k.a. generators).

Develop an inclusive community

The Hylo project aims to develop a programming language that is not only fast and safe but also simple. By simple, we mean that Hylo should be accessible to users from all sorts of backgrounds. A part of that objective lies in the language design, another in its community.

We’re happy to have already received contributions in the form of discussions, issues, and even pull requests on the code of our compiler. If Hylo is to survive, it is therefore that we continue to build an inclusive and welcoming community. To that end, we plan on developing the following axes throughout 2024.

Tooling

A language is only as strong as its tooling. We have already started working on a language extension for VS Code (see vscode-hylo). We also plan on developing a LSP server implementation.

Insightful error diagnostics

Good error diagnostics are essential to help developers write correct programs. We believe that Hylo’s model is amenable to developing insightful diagnostics and providing relevant suggestions.

We will take inspiration from Elm and Rust, which are both known for delivering great error messages.

Language and library documentation

Although we will have already delivered a specification of Hylo by 2023, we understand that typical users won’t expect to read that document to get started. Instead, a comprehensive language guide and user-friendly documentation of the standard library will help novices and experts alike get up to speed. Those resources will be published as an interactive website allowing users to run code directly on their browser.

Transparent process to follow and/or contribute

We strongly believe in the power of open source and the diversity of thoughts, ideas, and experiences. Not only will we commit to keeping our code and documentation publicly available, but we will also set up a transparent process to discuss the language evalution.

2025 and beyond

Total world domination?

---

Home