refactor: split monoiofs service into a separate crate#7038
refactor: split monoiofs service into a separate crate#7038koushiro merged 35 commits intoapache:mainfrom
Conversation
… via surrealdb service
There was a problem hiding this comment.
please revert irrelevant changes
There was a problem hiding this comment.
Thanks for the review.
There was a problem hiding this comment.
😕 You did not revert it; please do not run cargo update directly.
There was a problem hiding this comment.
Thanks for the clarification. I’ll revert the Cargo.lock changes caused by cargo update and push an updated commit.
Co-authored-by: Qinxuan Chen <[email protected]>
Co-authored-by: Qinxuan Chen <[email protected]>
You can get all you want to know from the prompts in #6829 |
Co-authored-by: Qinxuan Chen <[email protected]>
Co-authored-by: Qinxuan Chen <[email protected]>
koushiro
left a comment
There was a problem hiding this comment.
Mostly LGTM, but please revert the irrelevant changes in Cargo.lock
Co-authored-by: Qinxuan Chen <[email protected]>
No you didn't, are we really speaking the same language? |
a931032 to
3706a1f
Compare
You’re right—sorry about that. I hadn’t fully reverted Cargo.lock. I’m currently stuck on the remaining Clippy errors and haven’t been able to resolve them correctly. Could you please point me in the right direction on how these are expected to be fixed in this refactor? |
Which issue does this PR close?
Part of #6829
Closes #6909
Rationale for this change
This PR extracts the monoiofs service from
opendal-coreinto its own crateopendal-service-monoiofsas part of the core-split effort (RFC-6828). This improves modularity and compilation times by removing service-specific dependencies (like monoio,flume) from the core crate.What changes are included in this PR?
core/services/monoiofs.monoiofssource code fromcore/core/src/services/monoiofsto the new crate.monoiofssource and dependencies (monoio,flume) fromopendal-core.opendal-coreto remove the internalmonoiofsmodule.opendalfacade to re-exportMonoiofsfrom the new crate when theservices-monoiofsfeature is enabled.opendal_coreinstead ofcrate.Are there any user-facing changes?
No. The public API
opendal::services::Monoiofsremains exactly the same for users of the library. Internally, the code location and dependency structure have changed.AI Usage Statement
No.