Drop ostruct usage

[viralpraxis]

Resolves #124

I decided to try to make ServiceActor::Result a wrapper around hash instead of defining methods because 1) playing actors in sequence is basically about merging hashes, 2) it's just easier to implement and reason about, 3) I'd like not to to use metaprogramming if it's not required 4) that's basically how ostruct could be implemented (see ruby/ostruct#51 except BasicObject idea)

Seems like resolving #53 will be as easy as tweaking result's #method_missing/#respond_to_missing

@sunny could you please take a look?

[sunny]

That is awesome 😍 The final result is simpler, too 👏🏻

The spec failure on ruby head comes from the different error format in the next version of Ruby (TIL):

Expected:

undefined method `foobar='

Got:

undefined method 'foobar='

We can simply use a different matcher here to match all versions of Ruby, e.g.:

/undefined method ['`]foobar='/

Also, can you add a small entry to the CHANGELOG? 🙏🏻

[viralpraxis]

That is awesome 😍 The final result is simpler, too 👏🏻

The spec failure on ruby head comes from the different error format in the next version of Ruby (TIL):

Expected:

undefined method `foobar='

Got:

undefined method 'foobar='

We can simply use a different matcher here to match all versions of Ruby, e.g.:

/undefined method ['`]foobar='/

Also, can you add a small entry to the CHANGELOG? 🙏🏻

That ruby head issue is unrelated for this PR, I fixed it here: #128 (I'll rebase this one after merging that fix)

Added a note to changelog, see 1b97338

[sunny]

Thank you very much for this to-the-point clean refactor 👏🏻 ✨