fix clippy and format errors

Author: connortsui20

optd-core/src/operator/relational/logical/mod.rs

@@ -17,11 +17,11 @@ use scan::Scan;
 /// - `ScalarLink`: Specifies whether the children scalars are other scalar operators or a group id.
 ///
 /// This makes it possible to reuse the `LogicalOperator` type in [`LogicalPlan`],
-/// [`PartialLogicalPlan`], and [`LogicalExpr`].
+/// [`PartialLogicalPlan`], and [`LogicalExpression`].
 ///
 /// [`LogicalPlan`]: crate::plan::logical_plan::LogicalPlan
 /// [`PartialLogicalPlan`]: crate::plan::partial_logical_plan::PartialLogicalPlan
-/// [`LogicalExpr`]: crate::expression::relational::LogicalExpr
+/// [`LogicalExpression`]: crate::expression::LogicalExpression
 #[derive(Clone)]
 pub enum LogicalOperator<RelLink, ScalarLink> {
     Scan(Scan<ScalarLink>),

optd-core/src/operator/relational/physical/filter/mod.rs

@@ -1 +1,2 @@
+#[allow(clippy::module_inception)]
 pub mod filter;

optd-core/src/operator/relational/physical/mod.rs

@@ -18,10 +18,10 @@ use scan::table_scan::TableScan;
 /// - `ScalarLink`: Specifies whether the children scalars are other scalar operators or a group id.
 ///
 /// This makes it possible to reuse the `PhysicalOperator` type in [`PhysicalPlan`]
-/// and [`PhysicalExpr`].
+/// and [`PhysicalExpression`].
 ///
 /// [`PhysicalPlan`]: crate::plan::physical_plan::PhysicalPlan
-/// [`PhysicalExpr`]: crate::expression::relational::PhysicalExpr
+/// [`PhysicalExpression`]: crate::expression::PhysicalExpression
 #[derive(Clone)]
 pub enum PhysicalOperator<RelLink, ScalarLink> {
     TableScan(TableScan<ScalarLink>),

optd-core/src/operator/relational/physical/project/mod.rs

@@ -1 +1,2 @@
+#[allow(clippy::module_inception)]
 pub mod project;

optd-core/src/operator/scalar/mod.rs

@@ -13,12 +13,11 @@ use constants::Constant;
 /// - `ScalarLink`: Specifies whether the children scalars are other scalar operators or a group id.
 ///
 /// This makes it possible to reuse the `ScalarOperator` type in [`LogicalPlan`],
-/// [`PhysicalPlan`], [`PartialLogicalPlan`], and [`ScalarExpr`].
+/// [`PhysicalPlan`], and [`PartialLogicalPlan`].
 ///
 /// [`LogicalPlan`]: crate::plan::logical_plan::LogicalPlan
 /// [`PhysicalPlan`]: crate::plan::physical_plan::PhysicalPlan
 /// [`PartialLogicalPlan`]: crate::plan::partial_logical_plan::PartialLogicalPlan
-/// [`ScalarExpr`]: crate::expression::scalar::ScalarExpr
 #[derive(Clone)]
 pub enum ScalarOperator<ScalarLink> {
     Add(Add<ScalarLink>),

optd-core/src/rules/implementation/mod.rs

@@ -12,7 +12,7 @@ pub trait ImplementationRule {
     ///
     /// If the input expression does not match the current rule's pattern, then this method returns
     /// `None`. Otherwise, it applies the implementation and returns the corresponding
-    /// [`PhysicalExpr`].
+    /// [`PhysicalExpression`].
     ///
     /// Implementation rules are defined to be a mapping from a logical operator to a physical
     /// operator. This method is used by the rule engine to check if an implementation / algorithm