Konrad,
Thanks for the guidance, this makes a lot of sense - I was planning to
provide a method for printing these objects in the future anyway.
A bit of background: I'm trying to put together a simple framework
that uses structures to represent business-domain objects read from a
database, simi
On 27.04.2009, at 09:42, Meikel Brandmeyer wrote:
> AFAIU, struct-maps are not an optimisation for efficiency of the
> key lookup, but for the storage space of the keys. So "timings"
> should probably read "memstats".
If memory is the issue, then creating a single instance of the
metadata map
Hi Konrad,
Am 27.04.2009 um 08:44 schrieb Konrad Hinsen:
As for efficiency, I doubt that struct maps make that much of a
difference, but I didn't do any timings.
AFAIU, struct-maps are not an optimisation for efficiency of the
key lookup, but for the storage space of the keys. So "timings"
sh
On 27.04.2009, at 00:33, David Chamberlin wrote:
> I can get round this by not using a structure map for the metadata,
> but since I'm going to be creating container loads of these structures
> I understand that I need to be using struct-maps for efficiency.
>
> Is there a reason why this should n
I think I'm seeing some strange effects of some special handling
of :type in meta-data.
I'm trying to create a structure map with meta data that is also a
structure map. The meta-data includes the :type key, but I see an
error when I try to do this:
( def sm ( create-struct :type )
