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

Seal HasCompact + CompactLen #514

Open
bkchr opened this issue Sep 7, 2023 · 4 comments
Open

Seal HasCompact + CompactLen #514

bkchr opened this issue Sep 7, 2023 · 4 comments

Comments

@bkchr
Copy link
Member

bkchr commented Sep 7, 2023

Both traits should probably not be implemented by anyone downstream. We should check again, but the can be very likely be sealed.

@bkchr bkchr added this to the SCALE codec 4.0 milestone Sep 7, 2023
@bkchr
Copy link
Member Author

bkchr commented Sep 13, 2023

We should check the usage in ruint and then decide on what to do. Maybe HasCompact could also gets a better name 🙈 SupportsCompact? Or whatever. Maybe the entire trait structure is to complicated there and requires some rethinking.

@koute
Copy link
Contributor

koute commented Sep 13, 2023

Maybe the entire trait structure is to complicated there and requires some rethinking.

This is just my personal unsubstantiated personal opinion, but I do think we kinda have too many traits (this crates exports 20 traits in total!) that make things a little too complicated, so if we're going to do a breaking change release it'd be nice to redesign the API a little bit.

Of course this would be significantly more work than just patching things along in a backwards-compatible manner as we usually have done up until this point.

@bkchr
Copy link
Member Author

bkchr commented Sep 13, 2023

I mean we already had some breaking changes ;) Otherwise we would not have ended at 3.x. If you want to redesign it, do it :P

@koute
Copy link
Contributor

koute commented Sep 13, 2023

Yeah, I know. :P I don't know if I have the strength to do the redesign right now (but at least with the monorepo in place for Polkadot updating everything would probably not make me want to immediately want to gouge my eyes out), just wanted to voice my three cents. I'm not going to block 4.0 as-is or anything like that. :P (If the only breaking change is the one we had then the changes required downstream should be relatively minimal anyway.)

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

2 participants