Skip to content
This repository has been archived by the owner on Apr 24, 2019. It is now read-only.

Investigate EXINT encoding #8

Closed
binary132 opened this issue May 9, 2018 · 1 comment
Closed

Investigate EXINT encoding #8

binary132 opened this issue May 9, 2018 · 1 comment

Comments

@binary132
Copy link

Hi, this reminded me of something a buddy of mine wrote. I'm not sure whether this will be useful, but I thought I'd drop the link just in case.

http://dustinjuliano.com/2016/6/

@tiehuis
Copy link
Owner

tiehuis commented Jun 3, 2018

Don't believe this is too relevant here since we are typically more interested in faster processing and the overhead in encoding/decoding from a universal code would cause a slow-down in the hot loop. The possible stored size improvements are only interesting on huge integers and I expect that even then it would be negigible or evne worse than storing them directly, since typically the words of a big integer can be expected to be relatively random (if calculations aren't centered around a power-of-2 base).

Anyway, thanks for the link!

@tiehuis tiehuis closed this as completed Jun 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants