Skip to content

Releases: apple/swift-distributed-actors

0.2.3 More Actorable Polishing

12 Dec 04:52
0.2.3
Compare
Choose a tag to compare

0.2.3

Main features

Minor improvements in Actorable:

  • memory footprint of ActorableOwned<Reception.Listing<A>> improved
  • Actorables may be defined inside other types, e.g. Sensors.Actors.SomethingActorable etc

Stats

A total of 3 issues was resolved since 0.2.2, see them all on the 0.2.3 milestone: https://github.com/apple/swift-distributed-actors/milestone/9?closed=1

0.2.2 Actorable polishing

12 Dec 04:27
0.2.2
Compare
Choose a tag to compare

0.2.2

Stats

A total of 9 tickets was closed since 0.2.1, see them all on the milestone: https://github.com/apple/swift-distributed-actors/milestone/8?closed=1

0.2.1 - Codable conformance gen for Actorable.Message

29 Nov 02:53
Compare
Choose a tag to compare

0.2.1

Main features

  • GenActors now automatically generates Codable conformance for the Actorable.Message which is an enum with associated values. This means that types sent using Actorable are both enforced to be codable as well as everything "just works" if they are.
    • This feature will go away the moment we land "enums with associated values" conformance in Swift itself.
    • The conformance is generated into +GenCodable.swift suffixed files if you'd like to inspect it.

See the reference documentation for more details.

Stats

Since 0.2.0 a total of 6 tickets was closed, which can see listed on the 0.2.1 milestone.

0.2.0 Introduction of Actorable

19 Nov 14:25
0.2.0
Compare
Choose a tag to compare

0.2.0

Main features

  • Introduced Actorable and the associated GenActors command line tool.
    • this way of declaring actors is more declarative and simple to learn coming from plain Swift. It currently needs the source generation step, but perhaps we'd be able to avoid the need for it in the future.
  • Introduced LWWMap and LWWRegister CRDT types, as well as an Abstract Clock concept
    • Last Writer Wins CRDT types are plenty useful in simple scenarios where a value wants to be replicated for resilience, and risk of conflicts is low.

Stats

Since 0.1.0 a total of 29 tickets was closed, which can see listed on the 0.2.0 milestone.