Using NamedTuple instead of dictionaries

[AntonOresten]

It might be worth looking into whether setting properties in a NamedTuples can match the speed of dynamic dictionaries. Important note is that NamedTuple, like tuples, are immutable, and the tuple of properties would thus need to be instantiated for each modification, but maybe a package like Setfield.jl would make it easy (and fast?) to modify dynamic properties. My hope is that using NamedTuples would be more type-stable and lead to better performance (See #8). Since the property types of NamedTuples are embedded into the instance type, I guess the field would need to be a generic NamedTuple, which might undermine the potential benefits.

[Tortar]

I guess the field would need to be a generic NamedTuple, which might undermine the potential benefits.

I tested this strategy some time ago, and indeed, this seems to be the case, but if you want to double-verify this it would be great, maybe I did something wrong because I did it a bit in a hurry