Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reflections overhead #1

Open
KoNekoD opened this issue Aug 5, 2024 · 0 comments
Open

Reflections overhead #1

KoNekoD opened this issue Aug 5, 2024 · 0 comments

Comments

@KoNekoD
Copy link

KoNekoD commented Aug 5, 2024

Hello 😁

I think your reflection-based implementation is too overloaded with logic, you could make it even faster, but your example is more, hmm, more object-oriented, which is also quite nice

My implementation: https://github.com/KoNekoD/KSortMap-go

I, in turn, went the other way and simply defined them behind a common interface (those types that are quite easy to compare via > or < ) and this in turn became a simplification.

What do you think about my implementation, is it worth considering or is your version more productive/cleaner code?🧐

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant