David Owens II

@owensd isn't everything pretty much copy by default?

@chrisbrandow everything is a copy, yes. The question is, are you copying a value-type or a reference type? The code site is not clear.

@owensd none of them are reference, both Sets are values, ore immutable and other mutable. Also active verb like "remove" are mutating

@KostiaKoval @owensd basically what he said. Don’t think about pointers. Think about stuff being inside the variable itself.

@swizzlr @KostiaKoval yeah, you’ve missed the point. Had that type been MySet, you wouldn’t know unless you went to the type declaration.

@owensd @swizzlr I would try to understand use case. Set is data so I would "guess" that it's value but the only way to be sure is to check

@mustafa_ysf @KostiaKoval @swizzlr that assumes a code editor that can colorize based on those concepts; not all can.

@owensd Set is a struct. In Swift, struct is value, class is reference. I usually look in the documentation to check for that

@owensd Is there any language you know of which has explicit differentiation in code between passing by value vs reference?

@wczekalski any pointer-based language.

@owensd agree, but if you make a Set type in Swift with reference semantics you're doing something wrong