Hello Everyone,
Just wanted to let you know that we started a new podcast about Clojure:
https://defn.audio
We published our first episode and plan to release a new one every two
weeks. It is available on iTunes
https://itunes.apple.com/podcast/defn/id1114899563 and SoundCloud:
https://soundc
I think I will do something like this. Maybe instead of converting the
class name to a keyword, I'll just make a separate protocol IComponent or
something, that has a component-type function that returns a constant
keyword determined by the macro at compile time...
On Wednesday, 18 May 2016 15
Well, if you store it in metadata you'll have to look it up in the metadata
which is a hashmap lookup. As a method on a class it's a method call that
returns a constant.
On Wed, May 18, 2016 at 3:12 PM, JvJ wrote:
> Will it be much better than type metadata, though?
>
> On Wednesday, 18 May 2016
Will it be much better than type metadata, though?
On Wednesday, 18 May 2016 12:50:48 UTC-7, tbc++ wrote:
>
> Or define components to have a member called (name-as-kw [this]) returning
> a keyword version of the name of the type.
>
> On Wed, May 18, 2016 at 1:31 PM, James Reeves > wrote:
>
>> W
Or define components to have a member called (name-as-kw [this]) returning
a keyword version of the name of the type.
On Wed, May 18, 2016 at 1:31 PM, James Reeves wrote:
> Why not use the name of the class as the key?
>
> - James
>
> On 18 May 2016 at 20:02, JvJ wrote:
>
>> I'm creating an ent
Why not use the name of the class as the key?
- James
On 18 May 2016 at 20:02, JvJ wrote:
> I'm creating an entity-component-system architecture. To use it, you
> define component types, and put a bunch of components in a map to make an
> entity.
>
> The rule for entities is that they can only
I'm creating an entity-component-system architecture. To use it, you
define component types, and put a bunch of components in a map to make an
entity.
The rule for entities is that they can only have one component of any given
type, so I figured I would use the class to index it. However, sin
I don't think there's a general workaround, and I'm not sure I have enough
context to know what you are doing specifically.
On Wed, May 18, 2016 at 2:28 PM, JvJ wrote:
> I suspected as much. It would be possible to mitigate the problem by not
> using the repl, but I want the library I'm making
I suspected as much. It would be possible to mitigate the problem by not
using the repl, but I want the library I'm making to be built around a
repl-oriented workflow (like every good clojure library should).
Is there any way around this, or do I have to resort to :type metadata?
On Wednesday,
When you reload a namespace with a record, the class for that record gets
recreated. It will be functionally equivalent, but a different object.
I'll bet that classes hash on identity. (Though if they hashed on name,
you'd still have this problem.)
On Wed, May 18, 2016 at 1:31 PM, JvJ wrote:
>
I'm encountering a very strange error in some tests.
The details are a bit complex, but I'm using type-indexed maps.
So, given an object o, the map would be {(type o) o}. When I try to lookup
with the key (type o), I don't get the value, even though I can clearly see
it in the map.
I have a
Hi,
Just a quick update, we haven't planned a meeting yet but I'm hoping to
start one soon.
For the moment you can join me on http://slack.digitaloxford.com/ in the
#clojure channel,
and I'm also on the http://clojurians.net if you are interested to keep in
touch.
Thanks,
Kevin
On Tuesday, 15
12 matches
Mail list logo
