[Feature request] deliberately raise compiler errors & warnings about core HOT 1 OPEN

Currently we have alert pragmas, which are sufficient for scenarios A and B:

/// @alert unimplemented "don't call me now"
fn important_method(self: MyType) {
}

/// @alert deprecated "deprecated since 0.1.5 and will be removed in 0.2.0, use `refreshed_method()` instead"
fn old_method(self: MyType) {

}

For scenario C, perhaps the build system should be responsible for checking the building target. @lijunchen

The alerts are designed to be configurable. You can turn them off or treat them as compile errors by passing the -alert flag to the compiler. For example, -alert -unsafe@deprecated will turn off the unsafe alerts and treat deprecated alerts as errors.

The build system, moon, will support these configuration options in moon.pkg.json and moon.mod.json soon, so stay tuned!

from core.