What's wrong with returning both arguments? Seems to me that way it's more clear what is returned and the cast/indexing is unnecessary (those assume a type and slice size).
@fyrchik Could you clarify how much of S3 would you like to actually run in the local S3 scenario? I see the following possibilities:
- Use only the recently merged [NewTree](https://git.frostf…
even if it's a test error, can we use a more meaningful message?
I would simply remove all Get* prefixes, but up to you.
even though it's an in-memory implementation, can we use some meaningful error messages?
It seems that it was easier to use gomockery :-)
I agree :))
IMHO, neither the context should be stored in a struct (ctx docs discourage this explicitly) nor the state/functioning of the engine instance should depend on…
would it be simpler to just dump the registry in a format that is readable+explorable and performant already? (e.g. sqlite or whatever)
I see. But what I had in mind is that if you are calling LoadOrStore and there happened to be a value already (locked or otherwise), the mutex you just created and locked is never actually…