Tobias Gustafsson

Thanks for reporting this. I'll have to take a deeper look at this as I haven't been to involved in the work around typing. I don't know what's wrong off...

Hi! Thanks for opening this issue. The use case seems reasonable to me. Could you please create a PR with a suggested implementation for me to review (the gist looks...

Creating an umbrella issue may be good to keep things together although I think it would be fully reasonable to only implement parts of the characteristics described here. Keeping the...

Thanks @noahbenson! Yeah, looking into a speedier implementation of PMap would be nice. It's currently bolted onto the PVector to enjoy some of perf-benefits of that low level implementation while...

I'd be very interested in seeing what such a structure would look like. If it turns out to be a feasible replacement for the current PVector (feature-wise and perf-wise) I...

Thanks, keeping an eye on it! I guess some sort of hash collision handling must be implemented outside of the structure to make it usable for mappings (which is probably...

Seems cool, I can definitely see the use case. At first I was thinking that the type information should be possible to use for auto building default structures. It seems...

The only problem with that as I see it is that there are a lot of cases where such simplification would not be usable at all. For example when applying...

Sorry for the really late response to this. In general I think this would be a very nice functionality. I currently don't have the time to implement it (I believe...

Sounds like a good idea! I'm thinking along the lines of a public function (introspect?) taking the class as argument and calling a private method (**introspect**?) that does the actual...