vscode dscanner - struct initializer with named argument confuses DScanner #966

Activity

1. KaruroChori commented on Jun 24, 2025

   

   KaruroChori

   on Jun 24, 2025

   More actions

   As for my tests, the current version of d-scanner works well with named args. I think it is a downstream problem with the vscode extension.

   For reference, emitting the AST of

   module error;
   
   struct Type{
       int x;
   }
   
   int main(){
       Type(x:5);
   }

   results in no syntax error, even if the scanner used by the extension will complain:

   <?xml version="1.0"?>
   <module>
   <moduleDeclaration>
   <identifierChain>
   <identifier>error</identifier>
   </identifierChain>
   </moduleDeclaration>
   <declaration>
   <structDeclaration line="3">
   <name>Type</name><structBody>
   <declaration>
   <variableDeclaration>
   <type pretty="int">
   <type2>int</type2>
   </type>
   <declarator line="4">
   <name>x</name></declarator>
   </variableDeclaration>
   </declaration>
   </structBody>
   </structDeclaration>
   </declaration>
   <declaration>
   <functionDeclaration line="7">
   <name>main</name><type pretty="int">
   <type2>int</type2>
   </type>
   <parameters>
   </parameters>
   <functionBody>
   <blockStatement>
   <declarationsAndStatements>
   <declarationOrStatement>
   <statement>
   <statementNoCaseNoDefault>
   <expressionStatement>
   <expression>
   <unaryExpression>
   <functionCallExpression>
   <unaryExpression>
   <primaryExpression>
   <identifierOrTemplateInstance>
   <identifier>Type</identifier>
   </identifierOrTemplateInstance>
   </primaryExpression>
   </unaryExpression>
   <arguments>
   <argumentList>
   <argument named="x">
   <unaryExpression>
   <primaryExpression>
   <intLiteral>5</intLiteral>
   </primaryExpression>
   </unaryExpression>
   </argument>
   </argumentList>
   </arguments>
   </functionCallExpression>
   </unaryExpression>
   </expression>
   </expressionStatement>
   </statementNoCaseNoDefault>
   </statement>
   </declarationOrStatement>
   </declarationsAndStatements>
   </blockStatement>
   </functionBody>
   </functionDeclaration>
   </declaration>
   </module>