Thread overview
@target trouble with -w
Apr 13
Johan
April 09

I'm getting an apparently spurious warning, "ignoring unrecognized special parameter attribute ..." from ldc2 when passed the -w flag and using the @target attribute. Here's an example:

https://godbolt.org/z/vx6naWxYr

Code is generated correctly AFAICT when the -w flag is removed.

April 13

On Wednesday, 9 April 2025 at 02:26:18 UTC, Bruce Carneal wrote:

>

I'm getting an apparently spurious warning, "ignoring unrecognized special parameter attribute ..." from ldc2 when passed the -w flag and using the @target attribute. Here's an example:

https://godbolt.org/z/vx6naWxYr

Code is generated correctly AFAICT when the -w flag is removed.

Hi Bruce,
Please report it on github, thanks!

Johan

April 14

On Sunday, 13 April 2025 at 18:31:31 UTC, Johan wrote:

>

On Wednesday, 9 April 2025 at 02:26:18 UTC, Bruce Carneal wrote:

>

I'm getting an apparently spurious warning, "ignoring unrecognized special parameter attribute ..." from ldc2 when passed the -w flag and using the @target attribute. Here's an example:

https://godbolt.org/z/vx6naWxYr

Code is generated correctly AFAICT when the -w flag is removed.

Hi Bruce,
Please report it on github, thanks!

Johan

I resurrected my, forgotten, GitHub account and filed it. Thanks again Johan for the work you do on LDC.

Bruce

5 days ago

On Wednesday, 9 April 2025 at 02:26:18 UTC, Bruce Carneal wrote:

>

I'm getting an apparently spurious warning, "ignoring unrecognized special parameter attribute ..." from ldc2 when passed the -w flag and using the @target attribute. Here's an example:

https://godbolt.org/z/vx6naWxYr https://snow-rider.io/

Code is generated correctly AFAICT when the -w flag is removed.

You're right—this seems to be a warning triggered by LDC's stricter diagnostics when using -w, even though the code compiles and runs as expected. The issue likely stems from LDC not fully recognizing or supporting the @target("...") attribute syntax you're using.

You might consider filing a bug report or feature request with the LDC project if this isn't documented behavior. In the meantime, if -w is too noisy for your use case, a possible workaround is to suppress specific warnings if LDC supports that, or remove -w during development and enable it selectively in CI/testing.