Thread overview
[Issue 18829] pragma msg of int incoherent
May 11, 2018
Oliver Rümpelein
Nov 06, 2022
Dennis
Dec 17, 2022
Iain Buclaw
May 05, 2023
RazvanN
May 11, 2018
https://issues.dlang.org/show_bug.cgi?id=18829

--- Comment #1 from Oliver Rümpelein <oli_r@fg4f.de> ---
Here is an example, with the problematic line 14 commented out: https://run.dlang.io/is/xzgt0E

This fails with all primitive types.

I would expect the last line to just print "int", or give a useful error message that primitive types can not be used there, but it looks more like a logical error in the parser.

--
November 06, 2022
https://issues.dlang.org/show_bug.cgi?id=18829

Dennis <dkorpel@live.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dkorpel@live.nl
           Hardware|x86_64                      |All
                 OS|Linux                       |All
           Severity|normal                      |enhancement

--- Comment #2 from Dennis <dkorpel@live.nl> ---
According to the grammar, a pragma takes an argument list, which is a list of expressions. D has no first class types; a plain `int` is not an expression.

This is either an enhancement request to expand what pragma msg accepts, or to improve the error message when passing a basic type as an expression.

--
December 17, 2022
https://issues.dlang.org/show_bug.cgi?id=18829

Iain Buclaw <ibuclaw@gdcproject.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P1                          |P4

--
May 05, 2023
https://issues.dlang.org/show_bug.cgi?id=18829

RazvanN <razvan.nitu1305@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |razvan.nitu1305@gmail.com
         Resolution|---                         |WORKSFORME

--- Comment #3 from RazvanN <razvan.nitu1305@gmail.com> ---
This has been fixed. The code in the original bug report now successfully compiles outputting int in both situations.

--