-
Notifications
You must be signed in to change notification settings - Fork 156
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
Am/refactor/use natural decomposition order #1747
Conversation
a97223c
to
8b25aa9
Compare
8b25aa9
to
2adfe71
Compare
2adfe71
to
c163189
Compare
for @agnesLeroy focus on the GPU stuff |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks good to me as it is, I'm trying to come up with the corresponding change on GPU.
Draft PR here, let's see if the tests pass, if they do we can port the changes to this branch: #1749. Would be good to run benchmarks as well when the tests have passed to check it does not introduce a regression on performance. |
GPU tests are passing on the draft PR and benchmark results are not affected, we can go with it imo. |
ok @agnesLeroy should I include the patch in my PR ? |
Yes 👍 |
c163189
to
4b5aceb
Compare
impl Deprecable for ServerKey { | ||
const TYPE_NAME: &'static str = "ServerKey"; | ||
const MIN_SUPPORTED_APP_VERSION: &'static str = "TFHE-rs v0.10"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this really needed ? Since the different key types are each independently versioned, I'm not sure if we need to deprecate the higher level ones.
The deprecation will be caught during the deserialization of the inner type.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The same comment applies to all types that are not directly composed of a level container.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought about it but the error message would be less clear in that case if we don't do a mass deprecation, let me know what you think we should do, worse case I can revert some of the changes, but as they are done now does not matter much normally and I'd rather avoid unnecessary changes now to get the thing ready for the blockchain
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes makes sense, I think we can keep it like this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me !
- use natural order for decomposition levels in bsk co-authored-by: Agnes Leroy <[email protected]>
4b5aceb
to
f8b382b
Compare
No description provided.