RekordType not necessary

[grignaak]

It's limiting to require that Rekord only accepts types that extend/implement RekordType, and I don't see much benefit from it.

I suggest removing the constraints from all classes and methods.

[SamirTalwar]

Could you give me an example of how you would like to use it that is currently prohibited by RekordType?

[grignaak]

I can think of a few use cases.

Rekords would be perfect for metadata about objects--especially those which are from third-party objects. Take for example an HttpRequest, and you want to attach some timing metrics to the request, or some trace messages.

I could use Rekords to make builders for objects ala Make-it-easy. Again, very useful if the type being built was a third-party objects.

Mixing the above, Rekords could be used to map data-base columns to how to build an object. Or they could be used to transform database rows to a HttpResponse where the database columns and the output fields are named differently (shouldn't that be the case anyway?).

[SamirTalwar]

Those are all great use cases I hadn't thought about. Feel free to send a pull request. Alternatively, you're welcome to wait for me to do it. I don't think it will take me very long, but I might not get it done this weekend.