Skip to content

Conversation

@ndossche
Copy link
Member

@ndossche ndossche commented Sep 8, 2023

The entry points are duplicated: they add bloat and make it easier to forget to change something. Make maintenance easier by using @implementation-alias. Also, this has the nice side-effect of slightly reducing the amount of code and binary size.

…@implementation-alias

The entry points are duplicated: they add bloat and make it easier to forget
to change something. Make maintenance easier by using @implementation-alias.
Also, this has the nice side-effect of slightly reducing the amount of
code and binary size.
Copy link
Member

@Girgias Girgias left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't use the implementation alias thing, and the only time I saw it was to have a common implementation for a procedural and OO API, not between 2 "unrelated" classes.

@kocsismate is this use case supported?

@kocsismate
Copy link
Member

LGTM!

is this use case supported?

Yes, Phar and PharData has exactly the same use-case.

@ndossche ndossche closed this in f2fede5 Sep 10, 2023
@ndossche
Copy link
Member Author

Merged manually to resolve the conflict. Thanks y'all!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants