Add UI to toggle on/off loop protection comment

[davepagurek]

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:

[skyash-dev]

happy to take this up!

[harshiltewari2004]

Hi @davepagurek can I work on this?

[Jatin24062005]

@raclim can i work on this?

[harshiltewari2004]

Hi @raclim @davepagurek can I start working on this now?

[raclim]

Thanks for the interest in this issue!

Since @skyash-dev expressed interest first, I'll assign it to them. Once a PR is submitted, @Jatin24062005 and @harshiltewari2004 could take a look and provide a review into it if the both of you would be down!

[harshiltewari2004]

Thanks @raclim !

[skyash-dev]

hi @davepagurek and @raclim! im a bit unsure about the intended direction here.

should the source of truth be the presence of // noprotect in the user’s code, or should we rely on the preference flag and simply skip applying loop protection internally? (just like openprocessing)

since the web editor is often used by beginners, exposing a comment like // noprotect in their code might be a bit confusing. on the other hand, users who toggle this setting are probably little advanced.

what do you think?