module level log.fatal is not marked as @[noreturn]

[Le0Developer]

Describe the bug

log.fatal (NOT log.Log.fatal!) is not marked as @[noreturn]

Reproduction Steps

import log

fn mkerr() !string {
  return error("hi")
}

fn main() {
  a := mkerr() or {
    log.fatal('hello there!')
  }
  println(a)
}

Expected Behavior

Successful compilation, panic at runtime

Current Behavior

repro.v:9:9: error: `or` block must provide a default value of type `string`, or return/continue/break or call a @[noreturn] function like panic(err) or exit(1)
    7 | fn main() {
    8 |     a := mkerr() or {
    9 |     log.fatal('hello there!')
      |         ~~~~~~~~~~~~~~~~~~~~~
   10 |   }
   11 |     println(a)

Possible Solution

Simply add @[noreturn] to the function

Additional Information/Context

No response

V version

V 0.4.8 c1df71a

Environment details (OS name and version, etc.)

V full version: V 0.4.8 c1df71a
OS: macos, macOS, 15.1.1, 24B2091
Processor: 10 cpus, 64bit, little endian, Apple M4

getwd: /Users/leodev/v
vexe: /Users/leodev/v/v
vexe mtime: 2024-11-27 09:17:53

vroot: OK, value: /Users/leodev/v
VMODULES: OK, value: /Users/leodev/.vmodules
VTMP: OK, value: /tmp/v_501

Git version: git version 2.47.0
Git vroot status: c1df71a (22 commit(s) behind V master)
.git/config present: true

CC version: Apple clang version 16.0.0 (clang-1600.0.26.4)
emcc version: N/A
thirdparty/tcc status: thirdparty-macos-arm64 713692d4

Note

You can use the 👍 reaction to increase the issue's priority for developers.

Please note that only the 👍 reaction to the issue itself counts as a vote.
Other reactions and those to comments will not be taken into account.

_{Huly®: V_0.6-21426}