Default implementation for interface methods
Default implementation for interface methods
Interface methods can have a default implementation, so implementers do not have to implement newly added methods. Consumers get a warning that a default exists and can still implement their own logic.
Area: Developer tools. Status: GA. Developer relevance: high. Airtime: 3 min across 1 video, demoed.
Status evidence
- Nothing said about status; launch event convention: generally available unless stated otherwise.
Where they talk about it
- What's new in AL and Tools: 6:59 to 9:34, demo at 7:38
Quotes
- 7:59 "This is critical for allowing you to extend the interfaces over time." - Explains the design reason for default implementations on interfaces.
- 9:24 "So now with the default implementation we can extend an interface and build our solution across many releases without breaking any of our consumers." - Summarizes the outcome: interfaces can evolve without breaking implementers.
Documented features match
- Evolve AL interfaces with default implementations - high confidence (llm). Docs say: General availability, roadmap id 573352. Default method bodies on interfaces
Docs checked on 2026-10-02: the match is against Microsoft's what's new pages for the wave as they were on that date. Microsoft keeps filling the documentation, so "no documented item" can go stale. The wider product documentation on learn.microsoft.com was searched for this feature on the same date; the feature's data lists an article when one was found.
Tags: al, interfaces, language, extensibility
Generated by pipeline step 06. Source: YouTube auto-captions of the launch event videos, see the deep links. Not official.