Description

Currently, ThingsDB returns with the following error when a change is enforced and the nse() function is being called:

"function nse failed; at least one side-effect is enforced"

This can be annoying, as you sometimes want to create a closure which by itself does not require a change, but can be used in a scenario where a change is perfectly fine.

This PR removes the error and let nse() silently continue if a change exists.

Type of change

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

• Test collection functions

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• New and existing unit tests pass locally with my changes