Error Handling Strategies: Compile-Time vs. Runtime

[BhuvanB404]

Error Handling Strategies: Compile-Time vs. Runtime

Context

EdgeFlow currently emphasizes semantic validation during compilation, but many hardware constraints (memory limits, latency budgets) are only estimates.

This raises a key question:
Should the compiler block builds based on theoretical constraints, or allow users to accept risk?

Discussion Points

• Should insufficient memory always be a hard compile-time error?
• When should warnings be preferred over errors?
• How much responsibility should be pushed to runtime checks?
• How does strictness affect usability for research vs production users?

Goal

Define a consistent error-handling philosophy that balances safety, flexibility, and developer trust.