Circular Inheritance Detected on Something that isn't all that circular about boo HOT 4 CLOSED

It's a bug on the compiler, to detect cycles it checks if it has already visited a given base type as part of any inheritance path for the type being checked (Steps/Inheritance/BaseTypeResolution.cs). The fix is probably trivial, I'll play with it later on.

Two work arounds I can think of, the easier one is obviously to avoid the intermediate interfaces and just define the class like:

class ExhaustedCondition(ICondition, IAffectsStrength, IAffectsDexterity):

The second will keep the semantics of the original code but it requires separating in different assemblies the interface definitions from the type implementing them. This works because the compiler handles differently types defined in a compilation unit (internal) from those already compiled (reflected).

from boo.

Hi, yeah the reason I created the intermediate interface is so that I could have a list of objects that conform to the those interfaces. And as far as I know at least you can't do:

something as (IFoo, IBar)

Or can you?

Either way, my current workaround was to just remove ICondition completely and just put the method in all of the interfaces. Which isn't all too elegant but it works to achieve what I wanted.

Unrelated, but does anyone by any chance know how often Unity updates the boo version? So that I know roughly when the fix will be in Unity so that I can clean up the workaround.

Cheers! :)

from boo.

I'm afraid you can't express types that way, although it does actually look nice 🍺

As far as I know Unity uses their own fork of Boo instead of official releases. Perhaps you can point them to the fix and they can apply it to their fork.

from boo.

Ah so your commit fixed the bug? :)

If so I'll post an issue on their fork as well

from boo.