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.

Sign up for GitHub

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

Jump to bottom

Discuss tradeoffs involved when using static vs dynamic tables #46

Closed

dvdplm opened this issue Mar 27, 2020 · 1 comment

Contributor

dvdplm commented Mar 27, 2020

See #41 (comment)

Give users enough info to decide whether they should use static or dynamic tables, e.g. things like:

binary size
runtime memory (?)
cost of table generation
…

dvdplm mentioned this issue

Make static context a feature and allow dynamic context generation #41

Merged

trevor-crypto mentioned this issue

no-std support broken in 0.5.0 #71

Closed

Member

sorpaas commented Sep 15, 2021

Users can now choose themselves static-context vs lazy-static-context.

sorpaas closed this as completed

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