Nil Geisweiller

@linas, regarding > There is a performance hit: AtomTable holds a std::vector of length NUM_TYPES - That would need to be a hash table, and it could slow down atom-space...

> I would add that adding additional C++ Atom types in external libraries without modifying atomspace code would also be useful. Depending on what you mean I believe it is...

Even without auto-generated helpers to access in one language the types created in another, I still think it's a useful feature, but certainly it's not urgent we can give some...

Yes, I think automatic normalization may only concern basic equivalences, like the ones currently hard wired to detect scope link alpha-conversion. For more sophisticated stuff the URE should probably be...

@linas woudn't `PutLink` inherit from `LambdaLink`? https://github.com/opencog/atomspace/blob/master/opencog/atoms/base/atom_types.script#L263

By the same logic I think `ForAllLink` and `ExistsLink` should inherit from `LambdaLink`. Think of it that way, `ForAllLink` and `ExistsLink` are high level functions over predicates, basically one could...

Repeatability is great, lack of control not so great. Once in a while the user may need to set the seed. I guess it wouldn't have to be replaced by...

I think I get your point. Basically if we'd want to have the user reset the seed it would have to be via say a `SetRandSeedLink` or something, so this...

> The "set" will just be some atom, whatever the user wants, and the numeric value will just be a single float. Yes, that's the plan, intervals are just a...

> I kinda like it the idea of going more abstract, I'm just not sure where to go from there. I guess having a deeper look at sheaves could be...