Sean Collins

I think DM-ing the options makes sense!

> If someone is using their own structs (struct_namespace) there (even with a couple of methods inside), they will probably be caught off-guard by not being able to initialize them....

Great to hear! Maybe it’s more appropriate to think of `ROM::Struct` as a “Struct *Definition*” class rather than a Struct class itself (like how `Dry::Struct`, `::Struct`, `::OpenStruct`, etc. use the...

I think _most_ Structs in _most_ codebases (my impression) will have just one associated schema. Can we privilege that use-case, but still retain the power & semantic correctness of supporting...

Just ran into this same issue. A workaround I found is to specify `v0.19.1-4`, which has [a commit that added support for ARM (for macOS Silicon)](https://github.com/elm/compiler/pull/2156). It also added support...

Another idea for an API could be something like: ```ruby class MyGenerator include Dry::CLI::Colors def call puts Red["create"], " ", Green["lib/foo.rb"], " ", RGB["Main file", 55, 66, 77] end end...

We may also want to add bold, underline, etc: https://stackoverflow.com/a/42449998 Those could be extracted as `Dry::CLI::Styles` (either separately from `Colors`, or `Styles` could have them all together)

Looks like this can be closed, it was addressed in #311, though there was a comment that it should allow `nil` as an option stilll, which may have broken with...

In Elm this is called [`andThen`](https://package.elm-lang.org/packages/elm/core/latest/Task#andThen) (it's also what they call it for `Result` and `Maybe` too), so `and_then` could be another option. But, might be simpler to just stick...

Ah, sorry about that. Yes we'll release a new version with `helpers`. I'm not sure when though; it's not something I can do. I updated the title to be more...