Skip to content
This repository has been archived by the owner on Aug 19, 2020. It is now read-only.

Document SCALE Optimizations for Integer Types and Vectors Thereof #43

Open
danforbes opened this issue Apr 20, 2020 · 3 comments
Open
Labels
K6 - Advanced/Other Doesn't fit other K-labels. T3 - Enhancement A current page needs more info.

Comments

@danforbes
Copy link
Contributor

Document the concepts mentioned by @thiolliere in comments on #38.

@danforbes danforbes added K6 - Advanced/Other Doesn't fit other K-labels. T3 - Enhancement A current page needs more info. labels Apr 20, 2020
@gui1117
Copy link
Contributor

gui1117 commented Apr 21, 2020

Indeed maybe mentionning those optimization for the rust implementation (and so the one used in FRAME) of parity-scale-codec is interesting.
Also I guess we should document them in the code as well.

@bkchr
Copy link
Contributor

bkchr commented Apr 21, 2020

Okay, we speak here about the internal optimizations of the implementation? Why should they be documented here?

This is nothing a user should care about, this is just an optimization of the implementation.

@danforbes
Copy link
Contributor Author

I tend to agree with @bkchr. I think it is very important to be careful that we don't document too much because it will just confuse our users. Internal optimizations definitely fall into the realm of "too much" for me.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
K6 - Advanced/Other Doesn't fit other K-labels. T3 - Enhancement A current page needs more info.
Projects
None yet
Development

No branches or pull requests

3 participants