When designing an API, its authors have to consider many aspects: style, naming, scope, and implementation details are among these aspects. They have a direct impact on the resulting code, and its implementation can go in many different directions. How do you choose the best route to go? How do you guarantee consistency and performance across the framework? In this session, the mastermind behind Eclipse Collections (and previously GS Collections) shares the design choices he had to face and how he did it, the impact on different implementation strategies, and how the framework became a Eclipse project. Come take a look behind the curtains of a widely used API that has many years of development and that you can contribute to.
The slides from today’s talk:
The content for the slides in easy to read Markdown format:
Eclipse Collections website:
Eclipse Collections Project GitHub link:
Eclipse Collections Katas GitHub link: