Did you do something between the time it succeeds and the time it fails ?
I suppose I must have, but I have no idea what I did.
It's also possible that the error was lingering from the time before you declare the operation, but it should still run just fine.
Yes, it took me a while to figure out that sometimes errors just linger, even after I fix them. The error will sometimes stay in the log, even if the error doesn't even make sense anymore (e.g. I completely deleted the section that the error is complaining about).
But I'm certain that it's not only a lingering error, because I'll execute the program line by line to see what happens, and it will break on that same line and throw up the
operator is not a known binary operator error. (But other times I'll execute the exact same code, no typing at all, and it won't throw an error).
Do playground pages look at other playground pages? I'm experimenting with a lot of different things and so I have a bunch of playground pages in the same workspace with different versions of the same structs that I'm working on. I'm wondering if any of the redundant declarations from other pages are confusing the compiler. I have noticed that Playgrounds starts to slow down as I add more pages and code.