Jump to page: 1 2
Thread overview
Visual D showing weird errors
Apr 26, 2021
Raimondo Mancino
Apr 26, 2021
Imperatorn
Apr 26, 2021
Raimondo Mancino
Apr 26, 2021
Johann Lermer
Apr 26, 2021
Mike Parker
Apr 26, 2021
Johann Lermer
Apr 26, 2021
Mike Parker
Apr 26, 2021
Raimondo Mancino
Apr 26, 2021
Mike Parker
Apr 26, 2021
Imperatorn
Apr 26, 2021
Raimondo Mancino
Apr 26, 2021
Adam D. Ruppe
Apr 26, 2021
Raimondo Mancino
Apr 26, 2021
Rainer Schuetze
Apr 26, 2021
Imperatorn
Apr 28, 2021
Rainer Schuetze
Apr 28, 2021
Imperatorn
April 26, 2021

Hello, I'm new to the language; I just started learning it a few months ago. I'm doing okay with it, I find it very versatile and fast to learn. I come from Java and C/C++ and I think D solves tons of problems I had with these.

I was trying the Visual D extension to Visual Studio, but after the first code generation (DLL library, x86 & x64 both checked), I get this weird error:

C:\D\dmd2\src\druntime\import\core\sys\windows\dll.d:
\object.d(18): can only `*` a pointer, not a `typeof(null)`

So I opened the object.d in VS and apparently, this is the line of code it's yelling at:

alias noreturn = typeof(*null);  /// bottom type

I am unsure how to solve this problem. It doesn't appear to happen if I choose "console application" instead of "DLL Library".

Although, errors do appear if I try to inspect, for example, stdio.d:

Error: C:\D\dmd2\src\druntime\import\object.d(3460): template instance `object._dup!(const(char), immutable(char))` error instantiating
C:\D\dmd2\src\druntime\import\object.d(3438): instantiated from here: `_trustedDup!(const(char), immutable(char))`
C:\D\dmd2\src\phobos\std\exception.d(516): instantiated from here: `idup!(const(char))`
C:\D\dmd2\src\phobos\std\exception.d(437): instantiated from here: `bailOut!(Exception)`
--> instantiated from here: `enforce!(void*)`

and also:

Error: C:\D\dmd2\src\phobos\std\exception.d(437): template instance `std.exception.bailOut!(ErrnoException)` error instantiating
--> instantiated from here: `enforce!(shared(_iobuf)*)`

and others.

Since these are thrown by the standard library, I suspect this could be a bug; but maybe I'm just missing something?

Thank you for your help.

April 26, 2021

On Monday, 26 April 2021 at 08:00:08 UTC, Raimondo Mancino wrote:

>

Hello, I'm new to the language; I just started learning it a few months ago. I'm doing okay with it, I find it very versatile and fast to learn. I come from Java and C/C++ and I think D solves tons of problems I had with these.

[...]

What compiler and version are you using?

April 26, 2021

On Monday, 26 April 2021 at 08:40:01 UTC, Imperatorn wrote:

>

On Monday, 26 April 2021 at 08:00:08 UTC, Raimondo Mancino wrote:

>

Hello, I'm new to the language; I just started learning it a few months ago. I'm doing okay with it, I find it very versatile and fast to learn. I come from Java and C/C++ and I think D solves tons of problems I had with these.

[...]

What compiler and version are you using?

According to -v: DMD64 D Compiler v2.096.0-dirty

April 26, 2021

On Monday, 26 April 2021 at 08:58:25 UTC, Raimondo Mancino wrote:

>

According to -v: DMD64 D Compiler v2.096.0-dirty

Well, that says it all, doesn't it? I'm not familiar with the windows versions, but that doesn't seem to be an offical release - at least I never had a dmd2 that claimed to be dirty ;-)

April 26, 2021

On Monday, 26 April 2021 at 10:40:44 UTC, Johann Lermer wrote:

>

On Monday, 26 April 2021 at 08:58:25 UTC, Raimondo Mancino wrote:

>

According to -v: DMD64 D Compiler v2.096.0-dirty

Well, that says it all, doesn't it? I'm not familiar with the windows versions, but that doesn't seem to be an offical release - at least I never had a dmd2 that claimed to be dirty ;-)

That's actually normal for the Windows versions. I'm not sure where it comes from, but it's always there.

April 26, 2021

On Monday, 26 April 2021 at 08:00:08 UTC, Raimondo Mancino wrote:

>

Since these are thrown by the standard library, I suspect this could be a bug; but maybe I'm just missing something?

Thank you for your help.

You might try to build outside of VS and see if you get the same errors.

April 26, 2021

On Monday, 26 April 2021 at 10:44:14 UTC, Mike Parker wrote:

>

You might try to build outside of VS and see if you get the same errors.

The weird thing is that I get these errors just in the errors frame, but building works just fine without errors.

If I run devenv.exe directly on the solution, or select "build" from the menu, it builds fine; just, I don't get autocompletion or go-to-definition for some symbols.

Debugging works as well (although I see mangled symbol names, but I guess it's how it is supposed to work).

April 26, 2021

On Monday, 26 April 2021 at 11:03:19 UTC, Raimondo Mancino wrote:

>

On Monday, 26 April 2021 at 10:44:14 UTC, Mike Parker wrote:

>

You might try to build outside of VS and see if you get the same errors.

The weird thing is that I get these errors just in the errors frame, but building works just fine without errors.

If I run devenv.exe directly on the solution, or select "build" from the menu, it builds fine; just, I don't get autocompletion or go-to-definition for some symbols.

Debugging works as well (although I see mangled symbol names, but I guess it's how it is supposed to work).

Might be related to recent work on the semantic engine.

April 26, 2021

On Monday, 26 April 2021 at 11:03:19 UTC, Raimondo Mancino wrote:

>

On Monday, 26 April 2021 at 10:44:14 UTC, Mike Parker wrote:

>

You might try to build outside of VS and see if you get the same errors.

The weird thing is that I get these errors just in the errors frame, but building works just fine without errors.

If I run devenv.exe directly on the solution, or select "build" from the menu, it builds fine; just, I don't get autocompletion or go-to-definition for some symbols.

Debugging works as well (although I see mangled symbol names, but I guess it's how it is supposed to work).

Also, be sure to join on Discord as well (https://discord.gg/bMZk9Q4) if you're not already there!

April 26, 2021

On Monday, 26 April 2021 at 10:42:54 UTC, Mike Parker wrote:
(According to -v: DMD64 D Compiler v2.096.0-dirty)

>

That's actually normal for the Windows versions. I'm not sure where it comes from, but it's always there.

Ouuu, that's bad advertising, isn't it? Who wants to use dirty software, it could infect your computer... :-O

« First   ‹ Prev
1 2