Swi$and theEvolu&on

Swi$ is

Young

"… fully span the gamut of programming:…"

"from wri)ng the lowest level firmware…"

"up to the highest level applica0on programming." -- Chris La8ner

Timeline

Goals for 2.2Safety

Goals for 2.2• Quality-of-implementa0on improvements

• Finishing touches on 2.0 features

• Addi0ve (non-breaking) changes

• No fundamental changes to SwiE's use

• Depreca0ons in prepara0on for 3.0

Implemented proposals for Swi2 2.2• Allow (most) keywords as argument labels (SE-0001)

• Tuple comparison operators (SE-0015)

• Constraining AnySequence.init (SE-0014)

• Replace typealias keyword with associatedtype for associated type declaraEons (SE-0011)

• Naming FuncEons with Argument Labels (SE-0021)

Accepted proposals for Swi1 2.2• Add a Lazy flatMap for Sequences of Op8onals (SE-0008)

• SwiB Language Version Build Configura8on (SE-0020)

• Referencing the Objec8ve-C selector of a method (SE-0022)

Goals for 3.0Stability

Out of scope in 3.0• Full source compa.bility

• Concurrency

• C++ interop

• Hygenic macros

• New major library func.onality

Goals for in 3.0• Stable ABI + Resilience

• Portability

• Type system cleanup

• Complete generics

• Focus and refinement

• API design guidelines

Care and Maintenance of Our New Programming Language

Use the language

"You can only test it by looking at a large enough body of code and

seeing what problems they face." — Chris La*ner

Give what you can

Work toward understanding

Be willing to reframe your concern

The Core Team spends .me we don't 'see'

We had extensive internal discussions about proper4es, and made substan4al progress, but we do not yet have wording suitable for

the guidelines. Let me tell you where things stand.

— Dave Abrahams

Swi$ has a history

Time is a finite resource

• Use Swi)

• Research

• Don't hesitate

Swi$ is

Young

TJ Usiyan@griotspeak

Join the lists!h,ps://lists.swi2.org/mailman/lis7nfo