transpile: add comments clarifying the different but duplicative nature of the conservative and experimental const expr checks

Author: kkysen

c2rust-transpile/src/c_ast/mod.rs

@@ -626,6 +626,8 @@ impl TypedAstContext {
 
     /// Pessimistically try to check if an expression is `const`.
     /// If it's not, or we can't tell if it is, return `false`.
+    ///
+    /// This should be a top-down, complete, pessimistic analysis.
     pub fn is_const_expr(&self, expr: CExprId) -> bool {
         let is_const = |expr| self.is_const_expr(expr);
 

c2rust-transpile/src/translator/mod.rs

@@ -2140,6 +2140,13 @@ impl<'c> Translation<'c> {
             TranslateMacros::Conservative => {
                 // TODO We still allow `CExprKind::ExplicitCast`s
                 // even though they're broken (see #853).
+
+                // This is a top-down, complete, pessimistic/conservative analysis.
+                // This is somewhat duplicative of `fn convert_expr` simply checking
+                // `ExprContext::is_const` and returning errors where the expr is not `const`,
+                // which is an incomplete analysis scattered across all of the `fn expr_*`s.
+                // That's what's done for `TranslateMacros::Experimental`,
+                // as opposed to the conservative analysis done here for `TranslateMacros::Conservative`.
                 if !self.ast_context.is_const_expr(expr_id) {
                     Err(format_err!("non-const expr {expr_id:?}"))?;
                 }