And <@U3JQ35YQK>’s <https://www.youtube.com/watch?...

# gamedev

[orangy]

And @romainguy’s

https://www.youtube.com/watch?v=LJyDCYP0WG4▾

[orangy]

I’m slightly confused. Shouldn’t intersection be and and union be or?

[orangy]

I hope inline classes will be used for Color stuff in the new Kotlin code update: watched more, it is there

[orangy]

also inline classes for GLSL generic vec3 vs color or coordinates

[orangy]

inline var xy should probably be an extension property instead of a Float4 member?

[elect]

no, intersection is what is contained in both the operand

[elect]

and union is like a merge

[elect]

then following the same logic of bitwise operators, intersection requires or and union and

[elect]

1101 & 0111 = 0101

[orangy]

But your example shows clearly that & (and) returns an intersection of `1`s

[orangy]

Also, using math notation, a in (A union B) is the same as (a in A) or (a in B)

[orangy]

Like here https://en.wikipedia.org/wiki/Union_(set_theory)

[elect]

yeah

[elect]

I definitely need holiday

[romainguy]

Yeah there was a mistake in the slides

[romainguy]

It's fixed on speaker deck

[romainguy]

vec3 cannot be an inline class since it has more than one member

[orangy]

vec3 cannot be, but instead of vec3.r style, you could have color3 or something, which is inline class over vec3 and has these rgb properties

[romainguy]

To create new types yes

[romainguy]

But that's not what the swizzling and aliasing is entirely about

[romainguy]

Even if your vector a position you might want to address its components as RGB for visualization without wrapping it

[romainguy]

And the original goal was GLSL compatibility :)

[orangy]

Okay, here goes some reading on the topic… I’ll be back 🙂

[romainguy]

As for extension properties vs members, I can see either work. I'm not sure which would be better here

[romainguy]

I guess potentially extensions would mean a smaller class to load

[orangy]

Well, it will have to load the Kt class to use them anyway