lean-dependent-types

A "motive is not type correct" error in Lean 4 occurs when the rewrite tactic fails to resolve dependent type dependencies properly. Using advanced tactics like `congrArg` or `subst` can manage complex type interactions and resolve this issue.

Max recursion depth errors on `List.ofFn` and `Prod` in Lean 4 occur when `congr` or `rw` loops on nested structures. You can resolve these compilation errors by adjusting rewrite strategies, such as using `.trans` for transitive equality.

Cross-file visibility and namespace scoping errors in Lean 4 happen due to incorrect namespace management for new definitions. Applying `protected` visibility and ensuring proper namespace scoping allows correct definition access across different files.

The best way to rewrite large constants in Lean 4 without type mismatches is using `congrArg`. This tactic targets large constant rewrites specifically, avoiding the recursion issues and type mismatches that standard `rw` or `▸` might trigger.

You should use the `.trans` strategy in Lean 4 instead of standard rewrite tactics when dealing with transitive equality. It prevents rewrite failures with `▸` and helps avoid hitting max recursion depth on complex nested structures.