generics break global init order

[arnetheduck]

testit2:

proc inTestit2*[T](): T =
  var x {.global.} = inTestit[T]()
  echo "inTestit2: ", x
  x

testit:

import testit2

proc inTestit[T: int](): T =
  3 + inTestit2[int]()

echo inTestit2[int]()

[arnetheduck@tempus tmp]$ nim c -r --hints:off testit
inTestit2: 0
inTestit2: 3
3
[arnetheduck@tempus tmp]$ nim --version
Nim Compiler Version 1.4.2 [Linux: amd64]
Compiled at 2020-11-30
Copyright (c) 2006-2020 by Andreas Rumpf

git hash: 3fb5157ab1b666a5a5c34efde0f357a82d433d04
active boot switches: -d:release

notice how the first time around x has not had its initializer run yet. Of course, these kinds of circular inits are not sound, but the compiler should be able to detect them and ideally prevent them.

[arnetheduck]

also, shouldn't mixin be required for inTestit in intTestit2?