05:43 kjp left 05:44 kjp joined 05:45 kjp left 05:46 kjp joined
patrickb m: Q|1.&a; sub a() { }|.AST.EVAL 06:27
camelia ===SORRY!=== Error while compiling EVAL_0
Undeclared routine:
a used at line 1
patrickb So it's not the closures either. 06:28
m: Q|&a(); sub a() { }|.AST.EVAL
camelia ( no output )
patrickb Seems to be the sub as method call syntax itself. 06:29
I'm confused by Action methodop. It requires a longname to resolve a .& (to VarMethod), but in the grammar longname is explicitly disallowed for .& 06:44
If I read the code correctly, it will instead resolve to BlockMethod.
patrickb needs to read up on VarMethod and BlockMethod 06:45
I'd like to inspect this stuff in motion instead of only guessing by reading code. What's the best way to do so? printf-debugging? 06:48
Geth rakudo: rc-chuah++ created pull request #6065:
MSI: Use $(var.VERSION) For Product Version Instead Of Hardcoded "1.0.0"
09:42
rakudo/main: a9e53a05fd | (RC Chuah)++ (committed using GitHub Web editor) | tools/build/binary-release/msi/rakudo.wxs
MSI: Use $(var.VERSION) For Product Version Instead Of Hardcoded "1.0.0"

MSI: Use $(var.VERSION) For Product Version Instead Of Hardcoded "1.0.0"
Update tools/build/binary-release/msi/rakudo.wxs to use $(var.VERSION) for the MSI Product Version instead of the hardcoded "1.0.0". This resolves WinGet manifest validation errors (Manifest-AppsAndFeaturesVersion-Error) caused by successive installers reporting the same version. Relates to #6063.
  - Replace Version="1.0.0" with Version="$(var.VERSION)"
  - Ensure MSI ProductVersion matches Rakudo release
  - Prevent WinGet pipeline rejection due to duplicate versions
10:55
rakudo/main: 9c7aae8aed | (Patrick Böker)++ (committed using GitHub Web editor) | tools/build/binary-release/msi/rakudo.wxs
Merge pull request #6065 from rc-chuah/fix/rakudo-windows-msi-product-version

MSI: Use $(var.VERSION) For Product Version Instead Of Hardcoded "1.0.0"