[SR-11703] inlinable synthesised Equatable, Hashable, ... conformances #54111
Labels
bug
A deviation from expected or documented behavior. Also: expected but undesirable behavior.
compiler
The Swift compiler in itself
performance
Comments
|
@swift-ci create |
1 similar comment
|
@swift-ci create |
|
This would be appropriate for @Frozen structs and enums only. It probably shouldn’t be enabled by default — there is value in requiring user action to request inlinability. (A frozen struct may still reserve the right to change its hashing; e.g., consider Foundation.Data.) It would also make sense to allow additional attributes beyond @inlinable — should we implement a full C++-style `= default` syntax? |
|
@lorentey agreed. In the language dialect that SwiftPM uses (and therefore SwiftNIO) however, everything is |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Additional Detail from JIRA
md5: b1b48782af7210f46523fb8e5c4f37c1
Issue Description:
There is no way (known to us) to get a synthesised Equatable/Hashable conformance to be inlinable. It's a bit tedious to implement it manually just to get it inlinable.
Right now, it would always call into
static lib.Foo.__derived_struct_equals(lib.Foo, lib.Foo) -> Swift.Boolfor a typeFooin modulelibThe text was updated successfully, but these errors were encountered: