Entity ambiguous call

[sent44]

In v0.4.0

common.add(entity: EntityRef, componentList: varargs[typed])
common.add(entity: EntityRef, component`gensym107: ComponentTypeClass)

common.fetch(entity: EntityRef, components`gensym88: varargs[typed])
common.fetch(entity: EntityRef, component`gensym88: typedesc)

Workaround when add single component , pass with type; Cannot add with initialize value. When fetch single component, must pass object; I think this is bad to performance.

Remove these should work. I don't know other place that might have this ambiguous function.

polymorph/src/polymorph/statechanges.nim

Lines 817 to 818 in 14dd0d1

	template add*(`entity`: EntityRef, component: ComponentTypeclass) =
	`entity`.addComponent component

polymorph/src/polymorph/statechanges.nim

Lines 1081 to 1082 in 14dd0d1

	template fetch*(`entity`: EntityRef, component: typedesc): auto =
	fetchComponent(`entity`, component)

[rlipsc]

@sent44 Thanks for your issue with the workaround.

When I looked at my local code, I realised I've encountered the same issue and even created a commit, but hadn't pushed it.

Here's the commit: 0192baf

You may still need your removal of the fetch template for now, as locally I've solved this by changing the fetch macro to statically resolve to a single value when given one parameter, or a tuple for multiple parameters. This avoids leaning on the more ambiguous binding of the "middle layer" generic/template level.

I've got a few changes/fixes locally I need to upload, but haven't had the time to polish/finish them for commit until recently. For example, being able to make run-time lists of systems to execute for different work flows, and component types are (hopefully) better distinguished.