I, uh, actually kind of like the idea. If you just visually converted primitives to a toggle after you type true/false, and let you delete it like any other text, it could be a small convenience on any flags you might change during the development process.
Oh, I could easily see a trainwreck of an implementation. But if this was just a display option like color coding keywords and variables, but you could click to change the underlying true/false? I might add it.
As long as it’s not literally a toggle that you can interact with.
I can only imagine the horrors of accidentally clicking in the editor while selecting some text and quietly changing certificateIsValid = false; to true or something like that.
I, uh, actually kind of like the idea. If you just visually converted primitives to a toggle after you type true/false, and let you delete it like any other text, it could be a small convenience on any flags you might change during the development process.
I mean this as a joke but you might be right. A quick search suggests that no one implemented something like this yet.
As a visual indicator, sure.
Oh, I could easily see a trainwreck of an implementation. But if this was just a display option like color coding keywords and variables, but you could click to change the underlying true/false? I might add it.
More technical details in the full article ;)
Beatiful. Magnificent indeed
To actual posisble implementations, it’d actually be interesting as an indicator next to the bool to make it easier to see when debugging
As long as it’s not literally a toggle that you can interact with.
I can only imagine the horrors of accidentally clicking in the editor while selecting some text and quietly changing
certificateIsValid = false;totrueor something like that.Nah, make it a keybind like alt-shift-click and give it a deafening sound like throwing an industrial breaker.