Increasing Access
Loop protection currently breaks shaders (#4080) but there is not a clear way to fix the issue when it happens. Adding some UI to toggle on/off loop protection makes it more discoverable.
Feature enhancement details
Ideally the actual state being toggled just lives in the code. Similar to how the library version picker reads the HTML source code and changing the version changes the source code, a toggle for loop protection could add or remove the // noprotect comment.
As extra inspiration, here's what OP does:
Increasing Access
Loop protection currently breaks shaders (#4080) but there is not a clear way to fix the issue when it happens. Adding some UI to toggle on/off loop protection makes it more discoverable.
Feature enhancement details
Ideally the actual state being toggled just lives in the code. Similar to how the library version picker reads the HTML source code and changing the version changes the source code, a toggle for loop protection could add or remove the
// noprotectcomment.As extra inspiration, here's what OP does: