Annotations for the Complete Type (or Data::Record's Identity Crisis)

• problem-solving

  21 69 0.0

  🦋 Problem Solving, a repo for handling problems that require review, deliberation and possibly debate

  

Over time, most of the features that were a selling point for Data::Record have been rendered silly. Namely, the idea of a Tuple and Dict in core has been tossed about since writing, and the introduction of type inference for lists into core leaves most of the collections as which Data::Record is defined (Data::Record::Tuple, Data::Record::List, Data::Record::Map) with the odd edge case to cover, of which I don't feel it does a very good job of in its current release's state.

• rakudo

  55 1,700 9.9 Raku

  🦋 Rakudo – Raku on MoarVM, JVM, and JS

  

Over time, most of the features that were a selling point for Data::Record have been rendered silly. Namely, the idea of a Tuple and Dict in core has been tossed about since writing, and the introduction of type inference for lists into core leaves most of the collections as which Data::Record is defined (Data::Record::Tuple, Data::Record::List, Data::Record::Map) with the odd edge case to cover, of which I don't feel it does a very good job of in its current release's state.

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• ra-Data-Record

  2 4 0.0 Raku

  Record types!

The collections defined by Data::Record follow a pattern. The annotation is written as follows on the annotations branch:

Suggest a related project