VLS get_type_symbol invalid type about vls HOT 12 CLOSED

What code had you opened when you were trying to use vls?

from vls.

A fresh project with a lot of Win API interaction.
Do you need a code sample?

from vls.

module main

#flag windows -DWIN32_LEAN_AND_MEAN
#include <windows.h>

type HWND = voidptr
type DWORD = u32

type WPARAM = u64
type LPARAM = i64

type LONG = int
type UINT = u32

// https://docs.microsoft.com/en-us/windows/win32/api/windef/ns-windef-point
struct POINT {
	mut:
	x LONG
	y LONG
}

// https://docs.microsoft.com/en-us/windows/win32/api/winuser/ns-winuser-msg
struct MSG {
	mut:
	hwnd 		HWND
	message 	DWORD
	wParam 		WPARAM
	lParam 		LPARAM
	time		DWORD
	pt			POINT
	lPrivate 	DWORD
}

// BOOL RegisterHotKey(HWND hWnd, int  id, UINT fsModifiers, UINT vk);
fn C.RegisterHotKey(HWND, int, UINT, UINT) bool

// BOOL GetMessage(LPMSG lpMsg, HWND  hWnd, UINT  wMsgFilterMin, UINT  wMsgFilterMax);
fn C.GetMessage(MSG, HWND, UINT, UINT) bool

// void * memset ( void * ptr, int value, size_t num );
fn C.memset(voidptr, int, size_t) voidptr

fn main() {
	if !C.RegisterHotKey(C.NULL, 1, C.MOD_ALT, `b`) {
		println("Register Hotkey is invalid")
		return
	}

	msg := MSG{}

	for !C.GetMessage(&msg, C.NULL, 0, 0) {
		if msg.message != C.WM_HOTKEY {
			continue
		}

		println("Hotkey clicked!")
	}
}

from vls.

This and #89 are really hard to debug where to locate the offending function without the backtraces implemented other than TCC.

@alextwothousand can you try recompile VLS without -prod? Thanks

from vls.

This and #89 are really hard to debug where to locate the offending function without the backtraces implemented other than TCC.

@alextwothousand can you try recompile VLS without -prod? Thanks

I wasn't explicitly compiling with -prod.

Here is what I was doing to compile my program.

v -cc msvc main.v

from vls.

@alextwothousand I see. Can you recompile VLS using TCC (without specifying -prod or -cc flags) then? I meant that because compiling programs using the TCC compiler can produce backtraces and it's the only supported right now in V. I want to find out what made the VLS to trigger the get_type_symbol panic.

from vls.

I will give this a go at the earliest convenience.

from vls.

@alextwothousand It might be a Windows issue but the above code works fine on Linux.
@danieldaeschle If you have the time, can you diagnose this issue?

from vls.

I can attempt to try it in Linux? What distribution are you running— just for reference?

The fact that it's a Windows only issue is... interesting.

from vls.

I can attempt to try it in Linux? What distribution are you running— just for reference?

The fact that it's a Windows only issue is... interesting.

It is interesting. My distro is Ubuntu 20.04 64-bit

from vls.

I can attempt to try it in Linux? What distribution are you running— just for reference?

The fact that it's a Windows only issue is... interesting.

It is interesting. My distro is Ubuntu 20.04 64-bit

OK. I will attempt to reproduce this either on Fedora or Arch.

from vls.

Closing this as it is not applicable anymore to the current version of VLS.

from vls.