OvermindDL1

@korsmakolnikov You can work around it by returning a 2-arg function from your function directly, bit of a hack but it works.

> ` |> where(type: ^[:expert, :investor])` Doesn't this form lose type information of what is being processed on the struct? > ` |> where([i], i.type in ^[:expert, :investor])` Where this...

The definition of a component storage is that an entity belongs to it, not belongs to it multiple times. I'd have the internal data store be an array or list...

So it is the Abilities then? For those I'd probably make an Ability an entity that is parented to a card, just duplicate a base Ability blueprint for each one...

> Parent as in keeping a reference to an entity? In that case, is it safe to keep Entity references between update loop steps? I'd have a component on the...

I've been using hunter for years, *especially* for boost work (any other boost solution I've tried in cmake has been... painful, in comparison), so I can imagine how irritating it...

I think they are referencing like combining State and Writer monads as an example.

Isn't his example precisely what the readme states is how it should be used? https://github.com/witchcrafters/algae#constructor

> Hm, yeah, I definitely agree that's a useful feature! I was under the impression that Dialyzer does missing cases analysis, no? It misses a whole *ton* of cases. Dialyzer...

I'm actually more partial to OCaml style typing, it is easier to compile, faster to resolve, plus if you bring in the module system (which is entirely doable on the...