Joel Drapper

Starting over

3

Literal is full of so many half-baked experiments. These experiments have taught us a lot about what’s possible. I’m creating a branch called `legacy`, which will be locked to the...

- [ ] Figure out how to hook into code loading - [ ] Create a SyntaxTree processor for instance variable references - [ ] Ignore blocks protected by conditionals,...

Literal futures are a wrapper around [async](https://github.com/socketry/async) tasks, providing typed future values. ### Literal::Future You can create a future like this ```ruby future = Literal::Future(User).new { get_user_from_api } ``` It...

Implement `#as_pack` and `.from_pack` on `Literal::Data` and `Literal::Struct`

1

In addition to supporting Marshal, I think this is a sensible serialization interface. We can mostly just delegate to the existing `#marshal_dump` and `#marshal_load` methods, with allocation from the `.from_pack`...

`Literal::Some` and `Literal::Nothing` should implement `#value_or_raise!` and deprecate `value`

1

`#value_or_raise!` is so much more explicit about the risks of calling it.

I’m not exactly sure what Rails support will look like — and whether it should be in this gem or perhaps a `literal-rails` gem — but here are a few...

We can usually add some additional context such as the name of the attribute. Additionally, collection types could implement an alternative interface that allows them to highlight specifically which member...