Skip to content

suggestion: Allow for configuration of the maximum number of queued effects before infinite_loop_guard() is called. #16846

@michaelthoreau

Description

@michaelthoreau

I ran into an issue with a mapping project where a large number of components (thousands) are affected by an effect (infrequently).

It would be great to be able to increase the number of queued effects before the infinite loop guard comes in to effect (pun intended):

Currently:

if (flush_count++ > 1000) {
	// other code

	infinite_loop_guard();
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions