You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Swift supports a swift:attribute metadata, for adding attributes into the generated code. But, there's a major inconsistency in it.
The code-gen checks for this metadata on struct, but the validation rejects it on structs.
So, if you put swift:attribute on a struct, the validation removes it and warns you, even though the code-gen could of used it.
And the code-gen ignores this metadata on interface, but the validation allows it on interface.
So, if you put swift:attribute on an interface, the validation is happy, but it does absolutely nothing.
The documentation for this metadata says it's only supported on class, exception, and enum?
There is no mention of either struct or interface.
I'm not familiar with Swift, but only allowing it on class, exception, and enum feels like a weird list.
Should this be supported on struct?, on interface?, on anything else?
The text was updated successfully, but these errors were encountered:
Swift supports a
swift:attribute
metadata, for adding attributes into the generated code. But, there's a major inconsistency in it.The code-gen checks for this metadata on
struct
, but the validation rejects it onstructs
.So, if you put
swift:attribute
on a struct, the validation removes it and warns you, even though the code-gen could of used it.And the code-gen ignores this metadata on
interface
, but the validation allows it oninterface
.So, if you put
swift:attribute
on an interface, the validation is happy, but it does absolutely nothing.The documentation for this metadata says it's only supported on
class
,exception
, andenum
?There is no mention of either
struct
orinterface
.I'm not familiar with Swift, but only allowing it on
class
,exception
, andenum
feels like a weird list.Should this be supported on
struct
?, oninterface
?, on anything else?The text was updated successfully, but these errors were encountered: