-
Notifications
You must be signed in to change notification settings - Fork 362
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
Resolver patch #580
Resolver patch #580
Conversation
zokrates_core/src/compile.rs
Outdated
type FilePath = PathBuf; | ||
|
||
pub trait Resolver<E: Into<imports::Error>> { |
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.
Can <E: Into<imports::Error>>
go on resolve
rather than on the trait? I think it's good practice and it might also make things clearer
zokrates_fs_resolver/Cargo.toml
Outdated
|
||
[dependencies] | ||
zokrates_core = { version = "0.4.2", path = "../zokrates_core" } |
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 there a way to keep fs_resolver
independent from zokrates_core
? I guess having a different crate for that trait definition?
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.
We could introduce a "common" crate that contains the trait definition, and the trait should be more generic then.
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.
LGTM!
Added Resolver trait for code clarity